November 2, 2005 at 6:09 am
Hi!
Having this scenario:
- Windows 2003 Server SP1
- SQL Server 7.0
- An Access 97 .mdb file as linked server (locally, same machine).
When I try to browse the tables of the linked serv. it causes an error (7399... etc).
Sometimes everything works fine, sometimes not. Can't tell exactly WHEN. Doesn't seem to have a determined cause.
I noticed this happened to many people. Looking for a solution I did:
- Enable MSDTC (disabled by default)
- Reinstalling MSDTC
- Running "netsh ...etc" to enable the port (I also have disabled the firewall at all).
- Change some registry keys (also configurable from Component Services)
- Turned off RPC Security key on the registry
- Install the MSDTC Hotfix Rollup 6 (I had to call Microsoft for this...)
- The user for MSDTC is NTAuthority\NetworkService.
- In the configuration tab, Enabled almost anything.
- Read all the concerning MSKB articles.
And I can't still find the solution.
Anyone?
November 2, 2005 at 6:42 am
Have you rebooted the OS between changes?
November 2, 2005 at 12:10 pm
I rebooted, and rebooted, and rebooted, after almost every change.
I tried that MSKB workaround and some others though.
Also, I have COMPLETELY disabled the Windows firewall. It's still disabled.
November 3, 2005 at 9:11 am
Have you thought of upgrading to SQL2000 or SQL2005 ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 3, 2005 at 2:14 pm
According to Microsoft, this happens even on SQL 2000 (don't know about 2005). All the articles on MSKB are about SQL 2000.
And the problem appeared on Windows Server 2003, this ran perfectly on Windows 2000.
I guess it's a Windows Server 2003 problem.
(But concerns the SQL list, so keep posting!!!)
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply