2

I am getting internal server error when I am trying to browse OData service.

""error":"Internal Server error"

The initial issue was Update preview was not working on XPM. I double checked my lib folder, my config files as well as web.config and all files (Ambient and cartridges in Ambient XML). Even checked the DLLs.

I have re-verified the solutions which are given on other posts but even then this error comes.

Please help me on this and let me know if any information needed from my side. enter image description here

  • 2
    Anything in the EventViewer? Logs? – Albert Romkes Jul 22 '14 at 8:47
  • Look for warnings (!) from ASP.NET in your Application log under Event Viewer. You will see the real error and hopefully that will lead to easier troubleshooting. – Peter Kjaer Jul 22 '14 at 11:21
  • I have added an image for the log in event viewer. – user918 Jul 22 '14 at 15:19
  • Never seen this error. Doublecheck the IIS settings (SessionState), AppPool-settings. Is the latest version of the .NET framework installed? (And used: check AppPool settings) – Albert Romkes Jul 22 '14 at 19:17
  • WE are facing same problem. Can you please share the solution to your problem. Thanks. – Arash Nov 3 '15 at 13:56
1

Just check steps on following iconic post, it should resolve your issues.

http://albertromkes.com/2013/01/24/troubleshooting-the-sdl-tridion-experience-manager-with-session-preview/

| improve this answer | |
  • I have already re-verified these points as I wrote in my question. Even i set the same on others server which worked fine. – user918 Jul 22 '14 at 8:33
  • could you do a folder compare of all the config and jars with folder from working machine? do you see any difference? check logs as well – Raj Kumar Jul 22 '14 at 8:43
  • Have taken all jars and config from my other machine, have changed my storage file, deployer and licence files. my HTTPUpload worked so i can say my storage file is working fine. I can't find any logs related to this. – user918 Jul 22 '14 at 8:49
  • check log path in logback.xml in sessionService' bin\config folder, and check logs. – Raj Kumar Jul 22 '14 at 9:01
  • 1
    If your jars and config match a working one, then your error will have to be related to application server configuration or permissions of the user running the app pool. – Nuno Linhares Jul 22 '14 at 19:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.