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 |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2002-04-09 : 07:16:02
|
| Hi all, I have a scheduled task that runs an insert into a table on a linked server (serverA), whenever one of the client servers (say ServerB, ServerC, ServerD or ServerE) reboots. I have some jobs that run through sucessfully (each of the clients servers have run succesfully at least once). However, 2 of the server have had errors when running the job, and the job history for the step has the error:*******OLE DB provider 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399) [SQLSTATE 01000] (Error 7312). The step failed.*******Both of these server have also successfully runs this job after getting this erros, without any changes being made.According to BOL:*******Error 7399Severity Level 16Message TextOLE DB provider '%ls' reported an error. %lsCannot start your application. The workgroup information file is missing or opened exclusively by another user.ExplanationThis error message returned by the Microsoft OLE DB Provider for Jet indicates one of the following: The Microsoft® Access database is not a secured database and the login and password specified was not Admin with no password. The Access database is secured and the HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\SystemDB registry key is not pointing to the correct Access workgroup file. Secured Access databases have a corresponding workgroup file, including the full path, which should be indicated by the above registry key. ActionVerify that there is a login mapping for the current Microsoft SQL Server™ login to Admin with no password.If the Access database being accessed is secured, make sure that the above registry key points to the full pathname of the Access workgroup file.********I'm running SQL7 SP2 on NT4 SP5 on the client servers, and SQL2K SP1 on W2K SP2.Anyone got pointers for other causes of 7399? The job is reading the client servers logs to get the start time of the server, and the stop time from the previous log, and write them to a table on the central server.TIA |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-04-09 : 10:09:24
|
| support.microsoft.com ( which you should check in advance of BOL for error descriptions ) gives the following KB article for error 7399, which looked like it will be more helpful:[url]http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q314530[/url]In particular, the DBCC TRACEON command it recommends might help.setBasedIsTheTruepath<O> |
 |
|
|
|
|
|
|
|
Error 7399 - but I'm not using Access