failed during CreateProcess function call with error 183
I have Orbix6.3.4 on Windows 2008 and when I start a process I get these errors in the node_daemon log:
Thu, 21 Sep 2017 07:43:27.0000000 [ORBIXTV11:5024] (IT_ACTIVATOR:14) E - Process with Process ID -1 changed state to CREATE_PROCESS_FAILED.
Thu, 21 Sep 2017 07:43:27.0000000 [ORBIXTV11:5024] (IT_ACTIVATOR:61) E - Process "DS_GMOD6SUM" in domain "lamda.location" failed during CreateProcess function call with error 0: The operation completed successfully.
Thu, 21 Sep 2017 08:26:47.0000000 [ORBIXTV11:3152] (IT_ACTIVATOR:14) E - Process with Process ID -1 changed state to CREATE_PROCESS_FAILED.
Thu, 21 Sep 2017 08:26:47.0000000 [ORBIXTV11:3152] (IT_ACTIVATOR:61) E - Process "DS_GMOD6SUM" in domain "lamda.location" failed during CreateProcess function call with error 183: Cannot create a file when that file already exists.
As a result nothing is working for me. I have tried deleting and re-creating the domain and get the same error. Anyone know what might be going wrong?
I note that the current directory for that process is c:\test. By any chance does the orbix_test user not have write permission to that directory?
You can use
itadmin process modify DS_GMOD6SUM -directory <new dir>
to change this working directory for the process to see if that helps.
Can you modify -directory to another working directory as a test and then send on the output of itadmin process show DS_GMOD6SUM again?
I assume this was something that used to work in the past or is this a new installation on this machine? I also assume you are using the workaround of starting the process manually until you can resolve the automatic activation error?
Out of interest can you try and register a process for the simple persistent demo with the same user and working directory just to see if that works fine?
Thanks for your help and apologies for going quiet - I was inundated with people trying to help from all angles. In the end the root of the problem seemed to be associated with the recent installation of MKS on the server and the fact that 8.3 filename generation is turned off.
If you look at my post of the process show output (on 21 Sep 2017 10:20 )you will notice this:
The second line should be
So in the FAT the entry "Program Files (x86)" has PROGRA~2 as the 8.3 equivalent but "MKS Toolkit" does not have an 8.3 equivalent entry. There are a few other similar examples in the same list.
Removing MKS from the machine and removing these from the environment cleared up the problem.
Please don't hesitate in using our communities site to raise any further questions you might have.
Micro Focus SupportLine