We have a proprietary piece of software that uses .NET remoting technology. The remoting service has three parts: The executable, the dll, and the ini file to tell the service where the data is that it needs to get. I have taken the srvany.exe file and the instrv.exe files and placed them into c:\windows\system32\
I then created the service and made the appropriate registry changes. The service started without a problem. Ok, here is the weird part. The files for the service are on the E drive of the computer. The executable is designed so that if no INI file exists, it should create one. When I start the service, it does not see the INI file in the same folder with the executable and the DLL, so it goes to create one.... But it places it in the c:\windows\system32\ folder. Of course, the client can not connect because this ini file does not have the appropriate data. However, if I copy an INI file into the c:\windows\system32\ folder, the client functions properly. All the while, the service is not giving any error messages at any time. Is this an issue with Srvany.exe?
Any help would be greatly appreciated.