ODBC Connection Issue on Client Site

Hi,

It might be a basic question but could you please help me on that?

Working Environment:

I have developed application on SQL Server 2005 and now wants to Run on Client Site, I am using access as a front end and SQL server 2005 back end through ODBC (System Dsn) which is working good. (user has been added on SQL Server and on Database)

Question:

1) Do I need to create new System Dsn Or other DSN (Keep in mind I have already create System DSN in Server) at each client site to access application from Server?

(If yes then I am trying to do that, it allow me to create (with required database which is on Server) and verify but doesn’t save on ODBC list so I can’t use that name to run appliation on client site)

I am using windows authentication.

Thanks for help in advance

It's done the issue was admin rights on the client's computer.

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

Obscure linked server error

Hello,

I've got 2 SQL servers in a test environment - one is 2000 and the other is MSDE and they are seperate machines. I have added the MSDE server as a linked server to my 2000 box by issuing the following command:

EXEC sp_addlinkedserver '192.168.1.108', N'SQL Server'

I can query the database using an openquery in a select statement like so:

select * from openquery([192.168.1.108], 'select * from remote_test.dbo.products')

but when I try a direct query like the following:

select * from [192.168.1.108].remote_test.dbo.products

I get the following error:

An error occurred while executing batch. Error message is: Processing of results from SQL Server failed because of an invalid multipart name "192.168.1.108.remote_test.dbo.products", the current limit of "4" is insufficient.

I can't seem to figure out anything about this error. Anyone have any ideas?

Thanks,

Jeff Balcerzak

What about choosing another name than the IP ;-) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
--|||That does work if I specify the server name on my local network. If the production server is not going to be in the local network, would I create an alias to it with the public IP address?|||What about using an entry in the lmhost file to the outside IP?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||I actually added an entry in hosts file and created an alias to my public IP to test. I physically moved my test server to a different part of my network so it is not visible to the lan and created a port forward on my router to direct wan traffic on 1433 to the test server. Now when I execute the sp_addlinked server with the server name, it seems to work fine. Thanks for your help.