WebRecourse.WebRecourseFile

Question

WebRecourse.WebRecourseFile

dambalaji

SSC-Addicted

Points: 421
More actions
October 29, 2002 at 11:17 am

#158521

Hi,
I am having a problem with Createobject in my DTS package.
Set fileMaker = CreateObject("WebRecourse.WebRecourseFile")
Code works fine in Sql server 70 running on WINNT. But the same is not running on SQL 2000 running W2K. I am getting ActiveX component can't create Object error. Please advise.

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

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

dambalaji SSC-Addicted Points: 421 More actions · Answer 1

Here is the Continuation of the question.

The above code works fine when i run it from DTS package. But when I call the same DTS package from a Job , I am getting Active X Component can't create object .... Permission denied for CreateObject...

Please advice

mhweiss SSCarpal Tunnel Points: 4284 More actions · Answer 2

Have you checked the permissions that SQLServerAgent is running under? If the code runs fine under your user name but not as a job then you probably need to adjust the permissions for SQLServerAgent since this is the account that jobs would run under (as I understand it).

hth,

Michael

Michael Weiss

dambalaji SSC-Addicted Points: 421 More actions · Answer 3

This is the error message i am getting when i try to run the package from SQL job

Error Detail Records: Error: -2147220482 (800403FE); Provider Error: 0 (0) Error string: Error Code: 0 Error Source= Microsoft VBScript runtime error Error Description: Permission denied: 'CreateObject' Error on Line 7 Error source: Microsoft Data Transformation Services (DTS) Package

I Checked the permissions. All that looks good,Itis throwing error on the line CreateObject(Webresource)....

Note : webresource is the custom build ActiveX DLL for our internal use...

dambalaji SSC-Addicted Points: 421 More actions · Answer 4

I finally found the solution for this. It is explained very clearly in

Microsoft Knowledge Base Article - Q298725

Here is the breif explanation and resolution

SYMPTOMS

A Data Transformation Services (DTS) package containing a Microsoft Visual Basic Script task that calls CreateObject may fail when scheduled if the default access permissions in Dcomcnfg.exe have not been configured to include the SQLAgent account. These permissions are stored in the registry key HKLM/Software/Microsoft/Ole/DefaultAccessPermission. The log file for the DTS tasks will report:

Package Steps execution information: Step 'DTSStep_DTSActiveScriptTask_1' failed

Step Error Source: Microsoft Data Transformation Services (DTS) Package Step Error Description:Error Code: 0 Error Source= Microsoft VBScript runtime error Error Description: Permission denied: 'CreateObject'

Error on Line (xx)

Step Error code: 800403FE Step Error Help File:sqldts80.hlp Step Error Help Context ID:4500

This will only happen when the SQLAgent is running under a Windows NT logon account. This same package will run successfully interactively from the DTS designer or from DTSrun.exe or when scheduled if the SQLAgent service is running under the system account.

CAUSE

By default the registry value DefaultAccessPermission in HKLM\software\Microsoft\Ole does not exist. If an operator adds groups or users in default access permissions by using the DCOMcnfg utility, then the value DefaultAccessPermission is created.

If the account that SQL Agent is started with is not included in DCOMcnfg's default access permission, the package will return the error noted in the "Symptoms" section and the package execution will fail.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem do one of the following:

Use the DCOMcnfg utility to add the SQLAgent login account to allow access under DefaultAccessPermissions. To add an account, do the following:

Start DCOMcnfg.exe.

Click the Default security tab.

Click Edit default in the Default Access Permissions window.

Add the users as desired.

-or-

Delete or rename the HKLM/Software/Microsoft/Ole/DefaultAccessPermission key. WARNING: Note that this will effect the default permissions for all users on the computer. Before making this change ensure that this will not negatively effect any other DCOM applications on the computer. Although this will resolve the problem, Microsoft strongly recommends that you use the other resolution, described previously.

davidcote SSC Rookie Points: 40 More actions · Answer 5

Try checking the permissions on the file c:\winnt\sytem32\msvbm60.dll. After installing one of Microsoft's service packs, it sets the permissions. The file needs "Everyone" access.