IIS 5.0 to 6.0 migration / ASP DB Errors

Hello,

I currently have an ASP 2.0 Site running on Windows 2000 with IIS 5.0.

I need to transfer this site to a Windows Server 2003 box running IIS 6.0.

Here's what I've tried so far.

I copied the physical directory of the site on the IIS 5.0 box and transfered the directory to the same physical path on the IIS 6.0 box. From the IIS 6.0 box I then published a new virtual directory using the same name as the old one. I then restarted IIS and everything worked great accept the ASP Pages.

This was the error I got:



After doing a few Google Searches it was suggested that I insure that the IUSR_Servername account have read/write permissions on the following items:

-c:\windows\temp
-the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
-The directory containing the Access Databases.

None had this permission so I went ahead and assigned them. I then restarted IIS.

I got the same error.

I then decided to have the web site developer re-publish the website to the new sever location like he was publishing a new website.

After doing some it successfully made the ODBC connections and published the site to the new server under the same directory.

Unfortunately I still had the same error.

The only thing I have yet to try it reboot the server because possibly the registry change has yet to take effect.

If anyone has any ideas or maybe the locations of some revealing log files that would be terrific.

Thanks.

Also,

I should mentioned I didn't design this webpage or the databases and I normally don't administrer IIS or ASP servers, so if I forgot to include any critical information regarding my enviroment please let me know.

First, are you sure the db driver you're trying to use exists on the 2003 server? Support for access db's is less on 2003, and I'm not sure if the access odbc drivers exist on 2003.

However, your error message implies the drivers are there but the path to the .mdb isn't recognized. In addition to your other permission settings, did you check that the IUSR_ account has permissions to the folder and .mdb file itself?

Hi Doug,

Thanks for your reply.

I'm still new to this but here's what I did to check the Access Driver versions. I went under Admin Tools \ ODBC Manager \ Drivers

The 2000 box has Microsoft Access Driver 4.00.6306.00
The 2003 box has Microsoft Access Driver 4.00.6205.00

So it looks like 2003 has an older Access Driver. Do you think it's worth trying to update the 2003 box to the same driver version that 2000 has?

Or do you think I should wait and reboot to give the registry a chance to refresh itself after I applied ISUR_Servername write permissions to the ODBC Registry key?

Also, I made sure that IUSR has write permissions on both the access db folder and the actual dbs contained with in.

Thanks again for any suggestions.

I looked at your error message again. The problem seems to be that you are not giving any path to the database file in your connection string. What is your connection string?

If you're using a DSN make sure you've created an identical DSN for the connection on the new server.

I wouldn't do anything about the drivers versions, I was thinking about major version discrepancies. I doubt the minor build difference is an issue.

Thanks for continuing to look at this. I'm sorry but like I said I'm new at this and do not normally design ASP webpages from Frontpage for manage IIS Wev Servers.

Where could I check the connection string path? Is that set in the ASP files themselves? Or is that an IIS setting ?

Also DSN I understand is Data Source Name. However I do not know where you would set this information. Is this DSN location configured in each individual ASP file? Or is there some sort of master ASP Client Config file I should be looking at?

I deeply appreciate the help you've given thus far. The lightbulb in my head is starting to show signs of flicker. We're almost there.

Please let me know if you need me to post an example of the ASP code.

Thanks.

Oh wait!

I just found a file called global.asa.

Allow me to post a sample of what I think is the DSN information it and maybe you could tell me what you think by looking at it?

Hey I actually got this one figured out after searching Google for a few hours. Since you helped me out and kept me working on the problem, the least I can do is post the solution.

So in my last post I posted a DBQ from the Global.asa file. That turned out to be my issue.

To resolve the issue;

For every



I changed it to the local path



I then restarted IIS and everything's working like a charm.

Thanks again for all your help!

I'm happy to hear you got it worked out. Thanks for posting your solution.