CoInitialize permissions for windows service
-
We have a windows service executing on a windows 2003 box as the 'LocalSystem' account. This service spawns off a executable. The executable in turn tries to create an instance of a COM object housed in a dll. However we find that in a particular host,the executable fails at the point where it tries to intialize COM through CoInitialize. We believe it is due to some permission violations on the box. What are the services/permissions to be in place for a windows service account to be able to invoke COM?
-
We have a windows service executing on a windows 2003 box as the 'LocalSystem' account. This service spawns off a executable. The executable in turn tries to create an instance of a COM object housed in a dll. However we find that in a particular host,the executable fails at the point where it tries to intialize COM through CoInitialize. We believe it is due to some permission violations on the box. What are the services/permissions to be in place for a windows service account to be able to invoke COM?
The problem is that the application does not even start executing a single line and returns with a file not found error ;however when the same application is executed from console(and not from a service as 'localsystem' account),it executes fine. But we found that when we comment off the 'CoInitiliazie' call then things seem fine for the application (though we obviously cannot invoke COM)
-
The problem is that the application does not even start executing a single line and returns with a file not found error ;however when the same application is executed from console(and not from a service as 'localsystem' account),it executes fine. But we found that when we comment off the 'CoInitiliazie' call then things seem fine for the application (though we obviously cannot invoke COM)
So were you able to figure out what was wrong with CoInitialize?