ActiveX component can't create object - SQL2005 Agent Job

Question

Post reply

ActiveX component can't create object - SQL2005 Agent Job

sam patel

Old Hand

Points: 326
More actions
May 16, 2008 at 7:46 am

#207396

We are using SQL Agent ActiveX jobs to send MQ messages using
CreateObject("MQAX200.MQSession").
We are running this without any issues in SQL2000. When we upgraded to SQL2005 we are having errors as below. where STG is our domain and wfservice is part of Administrator group on this server.
Message
Executed as user: STG\wfservice. Error Code: 0 Error Source= Microsoft VBScript runtime error Error Description: ActiveX component can't create object: 'MQAX200.MQSession' Error on Line 23. The step failed
We are also using dome other FAX API and having same problem (can't create object) in SQL2005 but SQL2000 works fine.
Help!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

KenpoDBA SSCrazy Eights Points: 9811 More actions · Answer 1

That's because Yukon has tighter security than Shiloh.

Have you created a proxy and given it rights to active-x? That may get you what you're after.

Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant

Minion Maintenance is FREE:

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 2

Is the SQL Server 2005 server the exact same server as where you were running SQL Server 2000? In other words, did you do an in-place upgrade or did you install SQL Server 2005 to a new server?

K. Brian Kelley
@kbriankelley

sam patel Old Hand Points: 326 More actions · Answer 3

same server upgraded from SQL2000 to SQL2005.

This is 64bit server and could it be that when we ran with SQL2000 we used 32bit version of API DLLS and SQL2005 is running in 64bit mode and can not find API DLL's for 64bit.

Mohan.deval Say Hey Kid Points: 713 More actions · Answer 4

Hey Hi,

Can you mention which Tutorial ? I searched a lot on your blog / Ws... Pretty impressive,

Keep it up.

I have a similar issue, the Excel object creation written in script task works fine in debug mode , package execution from VS in release mode, but Not always 100% when exactly configured as a Job with a proxy account

from SQl Agent. Surprisingly the same SSIS packaged job executes creating an excel file on some rainy days but not when sunshines !!!!

I have created a Proxy account a administrator for SQL Agent SQL 2008 R2, but how would you give it rights to execute or create objects like active-x ?

I can send you my code snippet if you desire..

Thankx in advance...

Mohan.deval Say Hey Kid Points: 713 More actions · Answer 5

Was able to get pas thro' the Excel permission rights but still.... stuck in Cannot create ActiveX Component...... for Excel in SSIS SQL2008 R2, Windows 2008 R2 machine.. Sometime back I did something, that worked but still searching what I did...

Due to some DCOM permission settings for Microsoft Excel Application in Component Services. We need to run the command MMC comexp.msc, go to the properties of Microsoft Excel Application, under Identity, change it to The Interactive User from The Launching User (which is set by default). After making this change I was able to run the package as a scheduled Sql job successfully. However, there is still 1 little caveat when we are on x64 Windows 2008 (R2 also) Operating System where Component Services launched in 64 Bit does not show Microsoft Excel Application. In such a scenario we need to launch Component Services in x86 mode with the command MMC comexp.msc /32, rest of things remain the same.