Hi
I'm having a strange problem with a Webservice we built for an online solution with Navision 2009 R2.
The Webservice allows clients to download RDLC-generated Reports as PDFs and worked unchanged for the last 9 Months without a problem. Now i start getting these Errors after a while:
"Rendering output for the report failed and the following error occurred: The definition of the 'Main Report' is invalid."
which - according to google and the VS-community - is a problem when the issuing application can't access the proper dll's required for rendering the Report.
BUT: I can temporarely fix the Problem by restarting the Webservice. The Problem currently starts every two days or so once it happens all re reports fail to render until i restart the service again. Which is unacceptable du to the demanded 24h availability. So, I need to get to the root of this.
Thanks for the input
p.s. it gets even stranger: there is a second webservice running on the Server for the Test envoirement - which has no problems rendering the Reports while the otherone constantly throws errors. The involved Objects (two codeunits and the demanded Reports) are all on the same version (exchanged via *.fob import/export)
p.p.s i also had an issue yesterday where the webservice lacked the authority to write in it's own folder to regenerate the C# code after i recompiled the object:
"Compilation of XmlPort 50005 failed because of an I/O error on the following computer: [servername].[domain].local. Error details: could not find file '[Installation root]\Microsoft\Microsoft Dynamics NAV\60\Server\MycrosoftDynamicsNavServer$NAV2\assembly\XMLport50005_252.dll"
I fixed the problem by reassuring the rights of the Service on the Server-Folder and restarting the Service... I just thought this information might have something to do with the other issue and could be helpfull.
p.p.p.s. I am a developer at a solution Center and the issue is on a Customers server so it is reasonable to consider that their admins might have done or keep doing something in the configuration that messes with the Webservice.
0
Comments
here's a wild guess: some of the patches to the server (windows update) messed it up. We have a server running with several web services, and to ensure bad things don't happen we let it reboot every 24 hours. Sounds pretty old-school and hamfisted, but it fixed the issue. We intended to try out newer builds of 2009R2 to get rid of it, but with the fix in place there is no real pressure to do so.
with best regards
Jens
Reboot on this server is a no-go :-/ There are too many tasks running on it. Unfortunately the customer is not willing to spread the load on several servers ](*,)
I'm still looking vor a final solution.
regards StLi