Cluster and linked server to ms access | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Cluster and linked server to ms access

We are linking a SQL2000 server to an Access DB. We have set this up no problem on a normal SQL2K server – works like a treat. However, when we attempted to set this up with the same NT login on a SQL 2K Cluster any attempt to connect to the AccessDB fails with: Error 7399: OLE DB provider ‘Microsoft.Jet.OLEDB.4.0’ reported an error.
OLE DB error trace [OLE/DB Provider ‘Microsoft.Jet.OLEDB.4.0’ IDBInitialize::Initialize returned 0x80004005: ].

Does anyone know of any special problems with Linked Servers under SQL Clusters?

<br />Functionality vise SQL sever on Clustered environment is NOT at all a different SQL server then standalone/locally/independently installed SQL. Only difference here is hardware fault tolerance..[A/P]<br /><br /><br />Visit this link, you can resolve this problem: -<br /<a target="_blank" href=;EN-US;818182>;EN-US;818182</a><br /><br /><img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br /><br />Deepak Kumar<br /><br />–An eye for an eye and everyone shall be blind
I think Access software is not cluster aware.
In general the referred error using Jet database engine is caused
The Jet engine needs to create temporary files. To create the temporary files, the Jet engine uses the TEMP and TMP system environment variables. If the TEMP and TMP system environment variables do not exist, Jet uses the %WINDIR% folder. If the SQL Server service account does not have permissions to create, write, delete and read files in the %WINDIR% folder, or to the folder pointed to by the TEMP or TMP system environment variable, the error occurs. To work around this problem, use of the the following two methods. Method 1
1. Configure the TEMP and TMP system environment variables to point to a folder (for instance, C:TEMP).
2. Set the permissions to the SQL Server service account on this folder as Full Control.
3. Restart the server.
hTH Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Thank you for replies. Satya I guess it isn’t the correct reason because it doesn’t work Wanted to add couple situations when this linked server works when trying to connect to it from SQL server cluster: when I register SQL server with SQL login who has sa rights; when I place this mdb file on any of the cluster server; You may say that Windows NT account has not enough permissions the share where *.mdb are located. But it isn’t right, because I tried to do the same on non cluster server with the same win NT account and it worked. Any ideas? Thank you in advance