Re: oninit startup failure

MFLD wrote: > In response to Guy, > > Some asked details about my case: > > Is this the first time you've tried initializing after installation or > is this an existing instance which has just stopped working? > ---> It is the first time I initialize the server > > How much physical memory on this machine? > ---> 2 GB of physical memory > > Disk space ok? > ---> Yes, more than 30 GB free > > What is the exact IDS 10 version? > ---> 10.00.TC3 > > Are you running this directly or via Remote Desktop or some other remote > control software? > ---> Running oninit directly on the command line Nothing definitely wrong but some things to try: Your method is not generally how you initialise a Windows server which should be started using from Control Panel -> Administrative Tools -> Services with a special start-up parameter of "-iy". Having said this I would expect "oninit -ivy" to work, the trouble with this method is that if you close the command prompt window you kill the engine. Please try my method and let me know if you get different behaviour. Some things to try: Change SINGLE_CPU_VP to 1. Will probably make no difference though. Increase SHMVRTSIZE to at least 32768. 8192 is very low and the engine will probably need to add extra segments almost immediately. What else is running on the machine that could be using shared memory? Other than this I can see little wrong. We do this kind of thing all the time with no problems and I can't see from what has been supplied why yours is failing. Regards, Ben.