0

Not valid URL / Internal Server Error (500)

Jet Reports Historic Posts

February 25, 2013 13:58

None

Follow

Hi,

I've problem with connection about one week. Before that everything works OK. Here is the error:


I think it is problem with user profile(or just user), because all orther people can connect with to NAV with no problems just one user has problem with connection(tested on multiple computers).

Any idea?

Thanks for help.

Br,
Grega

• Facebook
• Twitter
• LinkedIn

6 comments

• 0
  
  Jet Reports Historic Posts February 26, 2013 19:13

  Hello,
  Two questions?
  Can you use your browser to get to the URL listed?
  Can you post a screenshot of your Microsoft Dynamics NAV Server Administration Tool Screen with the General Section open.
  Thanks,
  Joel

• 0
  
  Jet Reports Historic Posts May 02, 2014 09:05

  Hi,
  
  I have exactly the same problem now.
  One user get this error. All other can seamlessly connect.
  Wonder if you resolved this?
  
  Regards,
  Morten

• 0
  
  Jet Reports Historic Posts May 09, 2014 20:02

  Hello,
  Can you double check the data source settings for this user compared to a user that is working.
  Also check permissions in NAV.
  
  If you paste the URL from the error into I.E. is their more information regarding the error?

• 0
  
  Jet Reports Historic Posts September 17, 2014 08:24

  Hi,
  
  did you solve this? Struggling with the same erroro.

• 0
  
  Jet Reports Historic Posts September 18, 2014 22:34

  As noted in the documentation "Configuring Jet Essentials for Microsoft Dynamics NAV 2013" (available here –http://download.jetreports.com/KB%20Resources/Configuring%20Jet%20Essentials%20for%20Microsoft%20Dynamics%20NAV%202013.pdf) the "Jet Data Source" codeunit must be published to the Web Service.
  
  There are other Jet-related codeunits that must *not* be published. It appears that either a different Jet codeunit has been published under that name or all Jet codeunits have been published to the web service.
  
  In NAV, if you publish any codeunit to the Web Service with a public call that takes an object that's not allowed such as a RecordRef then it will cause substantial issues for ALL Web Services, not just the one with the bad method. This is what is generally what is happening here.
  
  All the currently-published, Jet-related codeunits must be UN-published and then the "Jet Data Source" code unit must be published following the instructions noted above.
  
  Once that is accomplished, please re-test.
  
  We have also seen other published codeunits conflict with the Jet codeunit. Un-publish everything in NAV but the Jet codeunit.
  When Jet starts working, add back each published Web Service until you find the Web Service that is conflicting with Jet.

• 0
  
  Jet Reports Historic Posts September 23, 2014 13:40

  Thank you, it was a different web service that caused the error.
  
  Cheers