I have a dll within a virtual directory on IIS 6.0 running Windows Server 2003 OS. The dll is called sqlcesa35.dll which is used by handhelds to sync data from a CE database to a SQL Express 2008 database on the server.
This dll is installed as part of installing Microsoft Server Tools 3.5. To test whether the virtual directory and dll is accessible, you simply type in the URL to the dll and it returns a message in the browser indicating success. So I can type and get a success message back.
So my problem is the following. For reasons that aren't worth detailing here, I need to make a copy of the dll and name it sqlcesa30.dll. I need this dll to be accessible just like sqlcesa35.dll. However, when I copy and rename the file, I can no longer access it within a browser. It always returns a 404 error, page cannot be found. I thought maybe it was losing permissions during the copy so I tried just renaming the existing file but when I do this, the original renamed file fails with the same error. So it appears to me that a dll is somehow registered by name and tracked by IIS 6.0. I have another server running IIS 5.1 and this does NOT happen. I can copy and rename the dll and calls to the renamed file return success message.
So what can I do on IIS 6.0 to access this renamed dll? Add a registry entry, append the new file name to an allowable dll list somewhere, create an installer of some sort to install the renamed dll, something else?? I'm sure it's some increased security in IIS 6.0 causing the issue but I desperately need to get around this issue as part of an upgrade strategy.
TIA!
J
This dll is installed as part of installing Microsoft Server Tools 3.5. To test whether the virtual directory and dll is accessible, you simply type in the URL to the dll and it returns a message in the browser indicating success. So I can type and get a success message back.
So my problem is the following. For reasons that aren't worth detailing here, I need to make a copy of the dll and name it sqlcesa30.dll. I need this dll to be accessible just like sqlcesa35.dll. However, when I copy and rename the file, I can no longer access it within a browser. It always returns a 404 error, page cannot be found. I thought maybe it was losing permissions during the copy so I tried just renaming the existing file but when I do this, the original renamed file fails with the same error. So it appears to me that a dll is somehow registered by name and tracked by IIS 6.0. I have another server running IIS 5.1 and this does NOT happen. I can copy and rename the dll and calls to the renamed file return success message.
So what can I do on IIS 6.0 to access this renamed dll? Add a registry entry, append the new file name to an allowable dll list somewhere, create an installer of some sort to install the renamed dll, something else?? I'm sure it's some increased security in IIS 6.0 causing the issue but I desperately need to get around this issue as part of an upgrade strategy.
TIA!
J
