March 26, 2002 at 11:55 pm
Hi all
I have a stored proc which calls a COM+ method, this routine generates around 50 data files (dumps from db) and takes around 3hrs. Example call:
exec @Hresult = sp_OACreate 'DATA_EXTRACT.PowerPlay', @Object OUT,4
<..etc..>
EXEC @Hresult = sp_OAMethod @Object, 'PowerPlayExtract', @v_returnval OUT, @v_startdate, @v_enddate, @p_emailto
about 3 to 4 mins into the job is stops with the error:
Error Source Description HelpFile HelpID
---------- ------------------------- ------------------------------- -------- -----------
0x80020011 ODSOLE Extended Procedure Does not support a collection. NULL 0
VB is returning NO error message unfortunatly except:
-2147352559
in @Hresult.
This com runs fine unside of SQLServer... which makes it all very strange.
Any ideas?
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
March 27, 2002 at 2:20 am
Fixed, #$%%@ developers havent been de-registering their com's correctly causing an OLD com to be retained, SQLServer was instanciating it. We have recompiled the com, cleaned the reg, re-started sqlserver and everything is now fine.
its only taken 2.5hrs!
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
March 27, 2002 at 4:57 am
I think you should take them out and flog the whole lot. Glad you found the problem though.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply