1

I have been setting up the OData Content Delivery for SDL Tridion 2011 and on a 64 bit environment. I am trying to host it in IIS but not able to browse the odata.svc. No error as such is shown on the browser, but in the back-end the app pool got stopped after some time. In the windows event log, I can see the error as shown below:

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0xc5c
Faulting application start time: 0x01d0d5ad25ad1ece
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 64f4a4a8-41a0-11e5-80bb-000d3ab06566
Faulting package full name: 
Faulting package-relative application ID:

Any help will be highly appreciated.

Improve this question
9
  • Did you use the pre-built Web Service role that is shipped with Content Delivery, or did you "build it" yourself? – Nuno Linhares♦ Aug 13 '15 at 10:21
  • I am using the pre-built one – Pankaj Gaur Aug 13 '15 at 12:23
  • do you see any other .NET related warnings in the event log before this error ? – Harald Hoffelinck Aug 13 '15 at 12:44
  • 2
    Are you installing on IIS 8.5 version: 8.5.9600.16384 and SDL Tridion 2011 ? It is not supported I believe and the issue could be very well related that .net + IIS 8.5 + Win OS.. – Ram G Aug 13 '15 at 12:46
  • do you see any error in IIS logs? – Raj Kumar Aug 13 '15 at 13:27
3

It seems like you are installing on IIS 8.5 version: 8.5.9600.16384 and SDL Tridion 2011 ? It is not supported I believe and the issue could be very well related the combination of .net + Juggernet + IIS 8.5 + Win OS .

Improve this answer
0
1

I would recommend checking the following:

  1. Check if IIS is configured to stop app pool if not in use for some time period.
  2. Using WinDbg to find out which area of the application is erroring out and parsing through app crash logs to find out areas of error
  3. Check the worker process thread and its memory consumption in IIS after app pool restart and monitor if the usage goes high.
  4. Also, check the CPU utilization on the machine to see if it is very high

Either one of the above should lead you in the right direction to solve the issue

Improve this answer
3
  • Thanks Vipin; already checked these items and all seems good – Pankaj Gaur Aug 13 '15 at 12:24
  • What error do you get when you try to browse odata.svc? – Vipin Kothari Aug 13 '15 at 13:12
  • No Error on browser. – Pankaj Gaur Aug 13 '15 at 13:57
0

can you check the cd_core log file of the odata webservice? I would expect that it logs any errors/warnings in that log file (preferably in debug mode).

Improve this answer
1
  • no error/warning logs in it – Pankaj Gaur Aug 17 '15 at 12:39

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.