Re: Access Linked server generates (Error 7399 / 7312)
- From: "PetitGosaimass" <PetitGosaimass@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Sep 2005 04:15:02 -0700
thank you. i'll try to trace the problem if it occuurs again. And let you know.
Thanks again
xavier
"Mary Chipman [MSFT]" wrote:
> I was thinking of SQL Profiler, which requires a sysadmin on the SQL
> Server box to set up and configure. If you could create a trace on
> just that one application, filtering out everything else, you might be
> able to narrow down where the problem occurs. It's possible that it
> might be an MDAC versioning issue. Check the boxes where it's
> occurring and see if there are any inconsistencies with boxes where it
> is working. As I said before, it's very difficult sometimes to
> troubleshoot issues where you don't have a reliable scenario to
> reproduce the problem.
>
> --Mary
>
> On Tue, 13 Sep 2005 03:11:04 -0700, "PetitGosaimass"
> <PetitGosaimass@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Hello
> >Regarding a trace...what should i do exactly ? Trace all requests, or simply
> >the error messages ? What for ?
> >Second, I was wondering if MDAC vesrion could be resposible for that. I
> >think SP on my actual server is SP1. It's a prod server, with big databases
> >and a cluster, that's why it is notyet with more adbvanced sp...need to
> >control all aplications for no regression. So i can't upgrade with a snap of
> >a finger.
> >What do you think i can try ?
> >Thanks a lot for your answers.
> >
> >"Mary Chipman [MSFT]" wrote:
> >
> >> I looked up the 7312 error number in SQL Books Online, and it says,
> >> (in English) "Invalid use of schema and/or catalog for OLE DB provider
> >> '%ls'. A four-part name was supplied, but the provider does not expose
> >> the necessary interfaces to use a catalog and/or schema." Since you
> >> are more familiar with the job in question, perhaps that message has
> >> meaning for you, or you can look it up in the French BOL. You might
> >> also want to create a SQL Profiler trace and see if you can capture
> >> the error. It's very difficult to troubleshoot errors that you cannot
> >> reproduce.
> >>
> >> --Mary
> >>
> >> On Thu, 8 Sep 2005 05:35:14 -0700, "PetitGosaimass"
> >> <PetitGosaimass@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> >Hello,
> >> >
> >> >I have two sql server 200O SP1 linked. A few jobs, running for separate
> >> >databases, execute a stored procedure which update a few tables of the
> >> >respective databases of the target linked server. The jobs are located on the
> >> >source server.
> >> >Most of the time, the jobs run fine. but there is sometmes an 7399 / 7312
> >> >error.
> >> >
> >> >The message i get is (soory, french )
> >> >Le fournisseur OLE DB 'SQLOLEDB' rapporte une erreur. [SQLSTATE 42000]
> >> >(erreur 7399) [SQLSTATE 01000] (erreur 7312). L'étape a échoué.
> >> >
> >> >I restarted the jobs when the problem occured, and they worked fine. I
> >> >thought about query timeout, but the remote query timleout is set to 0, so i
> >> >cannot be.
> >> >
> >> >Any ideas ?
> >> >
> >> >Thank you
> >> >
> >> >Xavier
> >> >
> >> >No trace was running.
> >> >
> >>
>
.
- References:
- Access Linked server generates (Error 7399 / 7312)
- From: PetitGosaimass
- Re: Access Linked server generates (Error 7399 / 7312)
- From: Mary Chipman [MSFT]
- Re: Access Linked server generates (Error 7399 / 7312)
- From: Mary Chipman [MSFT]
- Access Linked server generates (Error 7399 / 7312)
- Prev by Date: Re: Access Linked server generates (Error 7399) - Help!
- Next by Date: Re: Cast is not valid
- Previous by thread: Re: Access Linked server generates (Error 7399 / 7312)
- Next by thread: Query tables in two access databases with password
- Index(es):
Relevant Pages
|