Forum Discussion
sak
14 years agoOccasional Contributor
Hi Irina,
I have been given a higher priority task, so this issue is temporarily on "hold". :(
For what it is worth, a coworker pointed out to me that the service "proc1" is owned by" SYSTEM" (running Windows 2003, SP2) but the service "proc2" has been configured to "Log On" as another user so it can be remotely started by DCOM. The belief is that this problem has been seen before and that it may be related to a permissions issue.
I will probably pursue that idea once I'm back on this project.
Thank you.
Steve
I have been given a higher priority task, so this issue is temporarily on "hold". :(
For what it is worth, a coworker pointed out to me that the service "proc1" is owned by" SYSTEM" (running Windows 2003, SP2) but the service "proc2" has been configured to "Log On" as another user so it can be remotely started by DCOM. The belief is that this problem has been seen before and that it may be related to a permissions issue.
I will probably pursue that idea once I'm back on this project.
Thank you.
Steve
Related Content
- 4 years ago
Recent Discussions
- 12 hours ago
- 2 days ago