Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
db_sysadmin
Starting Member
27 Posts |
 Posted - 2006-10-09 : 11:09:33
|
| Hi,I attached a new linked server(Access 2000 database) to my SQL Server 2000, the mdb file is on the network path (\\computer\file.mdb) on on a windows 2000...I keep getting this error...Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.Authentication failed.What can I do? |
|
|
sponguru_dba
Yak Posting Veteran
93 Posts |
Posted - 2006-10-11 : 07:09:05
|
| Try this steps1. Log on to the computer by using the SQL Server start up account. 2. Create a folder named Temp in the operating system installation directory. 3. Permit full access to a non-administrator account on the Temp folder. 4. Set the value of the TEMP and TMP user variables of the SQL Server startup account to the newly created Temp folder. To do so, follow these steps: a. Right-click My Computer, and then click Properties. b. Click the Advanced tab, and then click Environmental Variables. c. In the User variables for Logon User list, click TEMP, and then click Edit. d. In theVariable Value box, type C:\Temp as the location of the new Temp folder, and then click OK. e. Repeat steps c and d to set the value of the TMP variable. f. Click OK two times. 5. Log off, and then log on to the computer by using SQL Server startup account. 6. Restart the SQL Server services. SreenivasaRao"Every Thought is Possible" |
 |
|
|
sponguru_dba
Yak Posting Veteran
93 Posts |
Posted - 2006-10-11 : 07:10:37
|
| This problem occurs because the login account does not have full access to the temporary folder of the SQL Server startup account. The linked server query runs in the context of the login account. If you run a linked server query, SQL Server tries to create a temporary file data source name (DSN) in the temporary folder of the SQL Server startup account.SreenivasaRao"Every Thought is Possible" |
|
|
|
|
|
|
Error 7399 -> Authentication failed