a connection error

Hi,
I have an error on my Application Server, it uses
analysis services and a SQL Server databases.
When I try to obtain information from the OLAP databases
it send me the next error:
Error Type:
ADODB.Connection(0x800A0E7A)
Provider cannot be found, It may not be properly
installed
Do you help me?
ThanksCheck to make sure you have MDAC installed properly on your app server

8198 error

sql2k sp3
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything. SA is the owner of all the
jobs.
Is there anything else I can do?
TIA, ChrisR
we are receiving these all over the place where I work. They are normally
solved by changing the job owner to sa and restarting the job. It seems that
a recent update has caused this problem/behavior.
"ChrisR" <noemail@.bla.com> wrote in message
news:%237FEr0PTFHA.3696@.TK2MSFTNGP15.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
> same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything. SA is the owner of all
> the jobs.
> Is there anything else I can do?
> TIA, ChrisR
>
|||It would have been easier if that had been it. I didnt realize that these
two boxes are in they're own little world, and that connections to them can
be rather difficult.
Thanks Hillary.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23B19ZdQTFHA.3464@.tk2msftngp13.phx.gbl...
> we are receiving these all over the place where I work. They are normally
> solved by changing the job owner to sa and restarting the job. It seems
> that a recent update has caused this problem/behavior.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:%237FEr0PTFHA.3696@.TK2MSFTNGP15.phx.gbl...
>