Could not create an instance of OLE DB SQL Schedule job fails

Hi,
There is a scheduled job on our SQL server that processes in 8 steps. The first step is to copy Excel files from  a template folder to populate it with the particular days date. The  rest of the step invoke stored procedures . The joba wwere running ok until yesterday when the first step is successful and the rest fail.
The error for the failed steps is
"Executed as user: NT AUTHORITY\SYSTEM. Could not create an instance of OLE DB provider 'Microsoft.Jet.OLEDB.4.0'. [SQLSTATE 42000] (Error 7302)  OLE DB error trace [Non-interface error:  CoCreate of DSO for Microsoft.Jet.OLEDB.4.0 returned 0x80040154]. [SQLSTATE 01000] (Error 7300).  The step failed."

ssosw2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ziolkoCommented:
0x80040154 is: Class not registered did you install/uninstall any software??

easiest way might be reinstalling MDAC components (just make sure you install correect one with jet engine) but check with MDAChecker before avali. here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en

ziolko.
0
ssosw2Author Commented:
I had done an installation for an HP printer LJ 4345
0
ziolkoCommented:
Class not registered means that some COM DLL is missing or is not registered, i don't think that printer driver would spoil OLE DB but you never know.

check MDAC version and re-install it if needed

ziolko.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ssosw2Author Commented:
Server restart got rid of the problem. Still not sure of the cause.
0
WPSLNetopsCommented:
I have the same problem in SQL2000 cluster , each time it happens I have to fail over to another node and problem goes away, but it come back again after few day!!

any solution other than re-start will be greatly appriciated.
Thanks


0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.