January 12, 2009 at 11:24 pm
hi all,
im using one script task which edits data present in a excel sheet.
the script working fine when im running the package.
but when i schedule the package, it throws an error that
"cannot create activex component."
i tried for
Shell("C:\Program Files\Microsoft Office\OFFICE11\Excel.exe", AppWinStyle.MinimizedFocus)
System.Threading.Thread.Sleep(20000) ' wait 10 seconds
excelApplication = GetObject(, "Excel.Application")
but still the same error... more over while schduling the excel application itself is not opening. it waits for 10 seconds and when the cursor comes to GetObject it is throwing the above said error... can anyone help me?
thanks in advance
January 13, 2009 at 9:04 am
mamsay (1/12/2009)
hi all,im using one script task which edits data present in a excel sheet.
the script working fine when im running the package.
but when i schedule the package, it throws an error that
"cannot create activex component."
i tried for
Shell("C:\Program Files\Microsoft Office\OFFICE11\Excel.exe", AppWinStyle.MinimizedFocus)
System.Threading.Thread.Sleep(20000) ' wait 10 seconds
excelApplication = GetObject(, "Excel.Application")
but still the same error... more over while schduling the excel application itself is not opening. it waits for 10 seconds and when the cursor comes to GetObject it is throwing the above said error... can anyone help me?
thanks in advance
Check here. Let us know if it worked.
January 18, 2009 at 11:29 pm
hi cozyroc,
writting data into excel sheet doesn't work.. so now i changed my proceedings.. it is throwing many errors.. i think writing the excel sheet through scheduling is not the right idea...
thanks for your valuable help cozyroc..
January 19, 2009 at 6:23 am
mamsay (1/18/2009)
hi cozyroc,writting data into excel sheet doesn't work.. so now i changed my proceedings.. it is throwing many errors.. i think writing the excel sheet through scheduling is not the right idea...
thanks for your valuable help cozyroc..
Can you tell us what errors it throws?
January 19, 2009 at 6:27 am
mamsay (1/18/2009)
hi cozyroc,writting data into excel sheet doesn't work.. so now i changed my proceedings.. it is throwing many errors.. i think writing the excel sheet through scheduling is not the right idea...
thanks for your valuable help cozyroc..
Did you read the thread CozyRoc linked to and attempt that solution?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
January 19, 2009 at 6:29 am
Is there an issue with authentication?
What is the authentication you used to test the script.
Check the authentication of SQL Agent
January 19, 2009 at 8:23 pm
hi all,
i have used two script tasks. one for writing something into an excel sheet and another one is for reading some data from the excel sheet. i disabled the script task which is writting data into excel sheet and try to schedule it by using proxy account. before one week it ran successfully. when i tried to schedule the script task which is writting data into excel sheet it is showing
cannot create activex component.
so i came to a conclusion that reading data from the excel sheet is less prone to errors. so i removed the script task which is writting. but now for script task which is reading data from excel sheet itself it is throwing
cannot create activex component.
but before one week i was able to schedule this task. in between i deleted and recreated the proxy and credentials many times.
what is happenning here?
i used windows authentication
thanks in advance
January 19, 2009 at 10:29 pm
hi cozy roc,
as per your guidence last week i created proxy account and it ran successfully. but now its not working. i'm getting mad. wat is the reason for this. i have deleted and re created credentials and proxies. i'm using windows authentication. please help me out.
now i'm getting the following error
The script threw an exception: Cannot create ActiveX component.
what i have to do now. last week this one ran successfully.
January 19, 2009 at 10:57 pm
hi wen i opend my package the following pop up appears.
do i need to install COM object. wat is that?
unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.IObjectWithSite'. this operation failed because the QueryInterface call in the COM component for the interface with IID '{FC4801A3-2BA9-11CF-A229-00AA003D7352}' failed due to the following error: The application called an inteface that was marshalled for a different thread. (Exception from HRESULT:0*8001010E_(RPC_E_WRONG_THREAD))
January 20, 2009 at 7:49 am
mamsay (1/19/2009)
hi cozy roc,as per your guidence last week i created proxy account and it ran successfully. but now its not working. i'm getting mad. wat is the reason for this. i have deleted and re created credentials and proxies. i'm using windows authentication. please help me out.
now i'm getting the following error
The script threw an exception: Cannot create ActiveX component.
what i have to do now. last week this one ran successfully.
Can you make the following test? When you run your job under your proxy account, have the same proxy account logged on to the machine at the same time. Let us know what happens?
January 20, 2009 at 7:50 am
mamsay (1/19/2009)
hi wen i opend my package the following pop up appears.do i need to install COM object. wat is that?
unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.IObjectWithSite'. this operation failed because the QueryInterface call in the COM component for the interface with IID '{FC4801A3-2BA9-11CF-A229-00AA003D7352}' failed due to the following error: The application called an inteface that was marshalled for a different thread. (Exception from HRESULT:0*8001010E_(RPC_E_WRONG_THREAD))
It looks like your SQL installation got corrupted. You may have to reinstall your SQL Server.
January 20, 2009 at 8:21 am
hi cozyroc,
my friend proposed this idea.. wil it work..
In run type
dcomcnfg.exe >>> on the left pane.. ther will be component services.. click on the '+'>>> my computer>>>COM+ Applications>>>Microsoft.SqlServer.MSMQTask… right click on this and go to properties>>>security tab>>>u wil get two options……The last lines must be this...
1. COM+ Security Call Context will not be available..
and
2.
COM+ Security Call Context will IS available……click the second one>>>>click ok leave everything else as the same... dont change anything
click ok...
close the component services..
then restart sql server service..
January 20, 2009 at 9:15 am
mamsay (1/20/2009)
hi cozyroc,my friend proposed this idea.. wil it work..
In run type
dcomcnfg.exe >>> on the left pane.. ther will be component services.. click on the '+'>>> my computer>>>COM+ Applications>>>Microsoft.SqlServer.MSMQTask… right click on this and go to properties>>>security tab>>>u wil get two options……The last lines must be this...
1. COM+ Security Call Context will not be available..
and
2.
COM+ Security Call Context will IS available……click the second one>>>>click ok leave everything else as the same... dont change anything
click ok...
close the component services..
then restart sql server service..
I don't know how this would help because this is a setting only for MSMQTask. Did you try what I suggested? Try running your job with specified proxy account and have the same proxy account logged on the machine at the same time.
January 27, 2009 at 10:59 pm
hi cozyroc,
that setting is the solution for this i think.. now its working.. and the cannot create activex component error is due to That COM object only i think.. after changing to this setting also if anyone gets the same error means then they need to re install their sql server. you are correct.
thanks cozyroc
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply