Windows service won't start on a different machine

Question

I created a windows service under Network service account that works fine on my local computer, dev environment. I want to test it on a different computer so i copied and installed the msi file from inside the setup project to a different machine. Checked Allow remote connections on my local MSSQLSERVER instance.

When i try to start the service - it says the service on local computer started and then stopped. sdome services stop automatically is they are not in use by other services or programs.

So i checked the eventviewer, it says - Service cannot be started.System.InvalidOperationException: Cannot open MSSQLSERVER service on computer <name>

This is urgent, any help is appreciated.

Thanks

Answer 1

It may be DCOM settings but I'd get in touch with the developer.

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Answer 2

I don't understand. Could you elaborate a bit more.

Answer 3

Some details here.

http://technet.microsoft.com/en-us/library/cc738214(v=ws.10).aspx

http://support.microsoft.com/kb/246054

http://support.microsoft.com/kb/176799

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Answer 4

I haven't created anything remotely related to DCOM. I have created a simple windows service in .net under network service account, that runs fine on my dev machine. It accesses the local database, looks up the subscriber list for the required events from a table and sends out an email to them. The config file for the service has the connection string for dev, test and prod servers. It works fine in dev machine with dev connection string. But doesn't work on a different computer:(

I don't know how to connect the dots between DCOM and my service.

Answer 5

don't worry about it Dave. looks like the application was accesiing sql server service that was making it to fail. That is figured out now.

Thanks anyway.

Answer 6

Good to hear its sorted.

 

 

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.