Unable to start Memory-Based Snapshot

Question

Hi all
I run into a problem that I'd been trying to fix it for 2 days. I am implementing and testing the an ASCP instance. I'd finished the Standard Collection, reviewed the collected data and everything is fine. I'd defined an unconstrained plan and launched this plan. The request "Launch Supply Chain Planning Process" completed and then "Memory-Based Snapshot" started. It failed immediately and give the following errors:
C:\oracle\R12\apps\apps_st\appl\msc\12.0.0\bin\MSCNSP
usdsop cannot create a new process
Cause: usdsop encountered an error creating a new process. [Reason].
Action: Check that your system had enough resources to start a new process. Contact your system administrator to obtain more resou (RE
Executing request completion options...
Output file size:
0
Output is not being printed because:
The print option has been disabled for this report.
Finished executing request completion options.
Concurrent request completed
Current system time is 22-SEP-2012 02:02:48
The platform is Windows 2003 server with 8G of ram (APPL_TOP with Conc. Manager). R12.1.3 with latest VCP patch applied.
I'd checked / done the following:
- relinked all MSC exe file in %MSC_TOP%/bin (no errors)
- Profile option MRP:Snapshot Workers = 3, and I have set Standard Manager to 15
- I'd checked all MSC and MRP profile options, cannot find anything special
- I'd run adconfig to make sure the environment settings are updated and no manual changes
- Run adadmin to make sure not invalid objects in the database
I'd another server with the same physical settings but running the VISION Demo (patched to have the same VCP level). I can launch the ASCP plan without any issue.
Can anyone tell me whether it is data issue, setting issue, hardware issue, or anything else ? Thanks.
Edited by: 960630 on Sep 21, 2012 11:22 AM

Answer 1

Thanks for your suggestions. I finally able to resolve this issue.
- I'd relink all MSC and MSO exe files. No error found. Still not unable to launch Memory-Based Snapshot.
- I'd turned on all possible debug, trace, etc to see any possible reasons for the failure. But no help at all.
I almost created a TAR (which will need to run numerous useless checkings, talking to some clueless people, and waiting for weeks for doing nothing) and I found out I forgot to check one place - Windows Event Log. Bingo - I found the error and it's because of DLL unmatched (typical Microsoft DLL hell issue).
Using Dependent Walker to see the linking of the MSC exe file, and then I pinpointed which version of MS C++ libraries were missed. Installed the latest MS VS2005 and 2008 redistributable libraries, relinked MSC exe files again, and FINALLY it's fixed.
I need to talk to the DBA who prepare this clone to me....
Edited by: 960630 on Sep 24, 2012 1:01 AM