Sage 100

CSODBC running as a service on a 2012 server. The service did not start automatically (although it was supposed to) after a server restart. The client's IT support was informed of this event. He noticed that the ""Path to Executable"" listed in the service properties is a UNC path. His comment: ""It cannot start until all the networking services are running. A service running on a local machine should never be running from a URL. That's the problem. Can you reach out to Sage about how we can re-install this properly?"" I don't believe there is any way to control the path during install. Do you IT folk and/or @AlnoorCassim have a comment or response I can give him?

I had this exact issue on my 2008 server. MY IT fixed it. Unfortunately, I was not paying attention. I will ask him to query the way back machine...

Client's IT support stated correctly. One could always fix by editing that path directly in the server's registry. Short of that just uninstall the service as a UNC then reinstall it using the local drive path methinks. Uninstall like this from the Windows Run prompt (don't me ask me how to get to the Run prompt in 2012 - perhaps Windows key + R). For example: ""\\Server\Share\Sage 100 Advanced ERP\MAS90\Home\pvxiosvr.exe"" -u (Use quotes above like I did if there is a space in the path) Then reinstall it via local drive. For example: ""D:\Sage\Sage 100 Advanced ERP\MAS90\Home\pvxiosvr.exe"" -i (Use quotes above like I did if there is a space in the path)