Access 2000
Windows Server2003
1. I had a Linked Server to an Access 2000 database which had worked for two
months.
2. Hoever, now when I execute queries againt it in Query Anayler, e.g.
SELECT * FROM LINKEDSERVERNAME...TableName
The query Analyzer just says "Executing query batch" and stays there for
several minutes. No error messages. Pressing red button to end query puts
QA into 'Progran not responding mode'. No error messages in QA.
3. If I go to Linked Server in EM and click on Tables or Views, most of the
time I get same thing - i.e. just hourglass for minutes.
Somtimes in EM when I click on Linked Server Tables or Views, I get Error:
Error 0: SqlDumpExceptionHandler:Process 51 (or 55) generated fatal
exception 0000005 EXCEPTION_ACCESS_VIOLATION. SQLServer is terminating this
process.
4. Only one time, time in EM, when clicking on Linked Server Tables, I got
Error 7339:OLE_DB Provider Microsfot.Jet.OLEDB reported an error.
5. I tried finding answers to this in Google, but to no avail.
Any help would be appreciated. Thanks.
AlanHi Alan,
Have you verified that the connection is actually being made to the linked
server? Check the process info on the destination server to see if a
process ID has been generated by your request. If not, then check your
firewall logs to see if your request is not making it to its intended
target. Hope this helps! Let me know what your results are and we can dig
deeper if need be.
-Jose
"Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
news:uR2IxZk$EHA.3988@.TK2MSFTNGP11.phx.gbl...
> SQLServer2000
> Access 2000
> Windows Server2003
> 1. I had a Linked Server to an Access 2000 database which had worked for
> two
> months.
> 2. Hoever, now when I execute queries againt it in Query Anayler, e.g.
> SELECT * FROM LINKEDSERVERNAME...TableName
> The query Analyzer just says "Executing query batch" and stays there for
> several minutes. No error messages. Pressing red button to end query
> puts
> QA into 'Progran not responding mode'. No error messages in QA.
> 3. If I go to Linked Server in EM and click on Tables or Views, most of
> the
> time I get same thing - i.e. just hourglass for minutes.
> Somtimes in EM when I click on Linked Server Tables or Views, I get Error:
> Error 0: SqlDumpExceptionHandler:Process 51 (or 55) generated fatal
> exception 0000005 EXCEPTION_ACCESS_VIOLATION. SQLServer is terminating
> this
> process.
> 4. Only one time, time in EM, when clicking on Linked Server Tables, I got
> Error 7339:OLE_DB Provider Microsfot.Jet.OLEDB reported an error.
> 5. I tried finding answers to this in Google, but to no avail.
> Any help would be appreciated. Thanks.
> Alan
>|||Jose,
Thanks for your quick reply.
1. I looked in sysprocesses of SQLServer tryin to do the select on the
Access Linked Server, and there are indeed records with Pricess ID for those
attempts.
2. I'll have to check with network admin about firewall logs.
3. Note1: This used to work! Does this fact help narrow down anything?
4. Note2: From Access ADP, I can still import tables from the MDB.
5. Is it possible that something got trashed in system table?s I've tried
dropping and recreating the Linked Server. It gets created, but still same
problem.
6. I've tried both regular Windows path as well as UNC path. Access mdb is
on same machine as SQLServer.
Regards,
Alan
"Jose Molina" <rcmaniac23@.yahoo.com> wrote in message
news:eAzoPvk$EHA.3120@.TK2MSFTNGP12.phx.gbl...
> Hi Alan,
> Have you verified that the connection is actually being made to the linked
> server? Check the process info on the destination server to see if a
> process ID has been generated by your request. If not, then check your
> firewall logs to see if your request is not making it to its intended
> target. Hope this helps! Let me know what your results are and we can dig
> deeper if need be.
> -Jose
>
> "Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
> news:uR2IxZk$EHA.3988@.TK2MSFTNGP11.phx.gbl...
Error:[vbcol=seagreen]
got[vbcol=seagreen]
>|||Hi Alan,
Have you tried dropping and recreating the linked server? Were there any
group policies implemented around the time you started experiencing issues?
I'm not sure where else to look. Try a post on the
microsoft.public.sqlserver.connect newsgroup to see if anybody else has
experienced this issue.
-Jose
PS Not to be condescending, but is the linked server set up correctly?
"Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
news:%23WGkpSl$EHA.3832@.TK2MSFTNGP10.phx.gbl...
> Jose,
> Thanks for your quick reply.
> 1. I looked in sysprocesses of SQLServer tryin to do the select on the
> Access Linked Server, and there are indeed records with Pricess ID for
> those
> attempts.
> 2. I'll have to check with network admin about firewall logs.
> 3. Note1: This used to work! Does this fact help narrow down anything?
> 4. Note2: From Access ADP, I can still import tables from the MDB.
> 5. Is it possible that something got trashed in system table?s I've tried
> dropping and recreating the Linked Server. It gets created, but still
> same
> problem.
> 6. I've tried both regular Windows path as well as UNC path. Access mdb
> is
> on same machine as SQLServer.
> Regards,
> Alan
>
>
> "Jose Molina" <rcmaniac23@.yahoo.com> wrote in message
> news:eAzoPvk$EHA.3120@.TK2MSFTNGP12.phx.gbl...
> Error:
> got
>|||Jose,
Thanks again for your reply.
1. Yes it was set up OK, because it was working for two months. I don't mnd
your asking.
I had dropped and re-created several times.
2. The network administrator rebooted server last night, and now I can do
SELECT on linked server. in Query Analyzer.
3. Something still off though, because in EM when I click on Linked Server
tables or views in tree, I get
Error 7399 OLE_DB Provider Microsoft.Jet.OLEDB.4.0 reported an error.
IDB Initialize: Initialize returned 80004005.
4. I just found KB 818182
PRB: Error Message: "Unspecified error" Occurs When SQL Server Accesses a
Linked Server That Uses Microsoft OLE DB Provider for Jet 4.0
5. This says using wrong version of Jet 4.0.
I'll have to check this out. Still strange since was working for two
months!
If problem persists I will try Connection group. I thought Security was
right one since that's where Linked Servers are.
Thanks again for your help.
Regards,
Alan
"Jose Molina" <rcmaniac23@.yahoo.com> wrote in message
news:#r44dSy$EHA.600@.TK2MSFTNGP09.phx.gbl...
> Hi Alan,
> Have you tried dropping and recreating the linked server? Were there any
> group policies implemented around the time you started experiencing
issues?
> I'm not sure where else to look. Try a post on the
> microsoft.public.sqlserver.connect newsgroup to see if anybody else has
> experienced this issue.
> -Jose
> PS Not to be condescending, but is the linked server set up correctly?
>
> "Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
> news:%23WGkpSl$EHA.3832@.TK2MSFTNGP10.phx.gbl...
tried[vbcol=seagreen]
e.g.[vbcol=seagreen]
query[vbcol=seagreen]
of[vbcol=seagreen]
terminating[vbcol=seagreen]
I[vbcol=seagreen]
>|||Hi Alan,
I agree that the post should be here, but just in case I thought you might
be able to get some additional information there.
Here is a thought... were there any updates recently that changed MDAC in
any way? My experience with MDAC has been that it is VERY temperamental.
Go figure...
Have you tried connecting from EM on other machines? The server itself? If
another machine works fine, check the MDAC version of the machine working
and compare it the one that is currently not working. Try looking at:
HKLM\SOFTWARE\Microsoft\DataAccess. You can always rollback the MDAC
version if need be on the machine you are having issues with. (That is if
there is a saved rollback version)
Check here for instructions on rolling back your MDAC version:
http://whidbey.msdn.microsoft.com/l...mdacinstall.asp
I'll continue to check with you to make sure we have a resolution to this
issue.
Regards,
-Jose
"Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
news:Ong%236my$EHA.2568@.TK2MSFTNGP11.phx.gbl...
> Jose,
> Thanks again for your reply.
> 1. Yes it was set up OK, because it was working for two months. I don't
> mnd
> your asking.
> I had dropped and re-created several times.
> 2. The network administrator rebooted server last night, and now I can do
> SELECT on linked server. in Query Analyzer.
> 3. Something still off though, because in EM when I click on Linked Server
> tables or views in tree, I get
> Error 7399 OLE_DB Provider Microsoft.Jet.OLEDB.4.0 reported an error.
> IDB Initialize: Initialize returned 80004005.
> 4. I just found KB 818182
> PRB: Error Message: "Unspecified error" Occurs When SQL Server Accesses a
> Linked Server That Uses Microsoft OLE DB Provider for Jet 4.0
>
> 5. This says using wrong version of Jet 4.0.
> I'll have to check this out. Still strange since was working for two
> months!
> If problem persists I will try Connection group. I thought Security was
> right one since that's where Linked Servers are.
> Thanks again for your help.
> Regards,
> Alan
> "Jose Molina" <rcmaniac23@.yahoo.com> wrote in message
> news:#r44dSy$EHA.600@.TK2MSFTNGP09.phx.gbl...
> issues?
> tried
> e.g.
> query
> of
> terminating
> I
>
No comments:
Post a Comment