13 Replies Latest reply: Mar 11, 2013 1:20 PM by Mohamed Rashid RSS

unable to run 32 bit SSIS package on 64-bit 2008 WIN server

Mohamed Rashid

Hello,

 

Has anybody faced the error while running  32bit SSIS package on 64bit 2008 SQL Server on  WIN 2008  server where CTMAGENT+CM DB of 64 - bit is installed.

 

 

Currently SSIS packge is running on the SQL server with an option 32 bit .

  • 1. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    dkaris

    Hello,

    What kind of error are you getting?

     

    We do have the opposite scenario, agent and cm for databases running on 32 bit. We do have an account pointing to a 64 bit sql server.

    In our scenario all SSIS packages are defined as file system packages.

     

    No issues so far.

     

    If possible post some more details.

    Regards

    Dimitris

  • 2. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    Thanks Dimitris,

     

    my agent  and cm for databases running on 64 bit and SQL Server 2008 is 64-bit, SSIS packages are defined as file system packages, below is the error,

     

     

     

            ERROR: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.1 is not registered -- perhaps \

    no 64-bit provider is available.  Error code: 0x00000000.

    An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registe\

    red".

     

    Currently SSIS packages are run on the SQL server with an option clicked on 32bit.

     

    to execute the SSIS packge , is it not mandatory to have CM DB locally where DB lies?

     

    is there any option on the account to be 32 bit or 64 bit account?

     

     

    apprecite if you could help on this.

  • 3. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    dkaris

    Hello Mohamed,

    for sure you can install the cm for databases on any agent you like, not only on the one running on the database server.

    As for the account i do not think there is an option for 32 or 64 bit.

    As for the error, have you tried to contact BMC support?

     

    Regards

    Dimitris

  • 4. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    Thanks for you reply..

     

    Just wanted one thing..

     

    Does the DB CM interacts commands execution?

     

    i meant to say when we run any SSIS job from control-M job with CM DB , does it run from  command level?

     

    how they are getting executed any Database JOBs by CM DB from control-M?

     

    does it with the help of lib of CM DB or ?

     

    thanks

  • 5. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    Hi Dimitris,

     

    Just to understand one things?

     

    we have alots of DTX packges running on SQL server 64 bit with the help of sql server agent in 32 bit mode.

     

    and i have installed Control-M agent on the same server ( windows 2008 64 bit ) ,, but  when i defined account and when  i running the job i am getting the error

     

            ERROR: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.1 is not registered -- perhaps \

    no 64-bit provider is available.  Error code: 0x00000000.

    An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registe\

    red".

     

     

    I am sure above error because Control-M job is trying to run on 64 bit mode instead of 32 bit mode.

     

    Can we install the Agent 32 bit server and CM DB and point to the SQL server 64 bit then run the DTX jobs?

     

    Thanks

  • 6. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Nicholas Starinsky

    try running it with 32-bit dtexec first on the box where agent CM for DB is installed, under service account that your Control-M CM for DB account is set to run. It should fail. From Microsoft - set RUN 64  BIT RUN TIME to FALSE on project properties.

  • 7. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    WhiteLady

    Hi Mohamed,

     

    Are you trying to run the SSIS package using the Control-M for Database (execution type SSIS package) or as an OS job using the DTEXEC utility?

    If you are trying the SSIS solution, first make sure that the account you created passes valiadtion correctly.

    Regarding the Agent 32/64 bit, if you are using a 64 bit machine, you cannot install Agent 32 bit on it, the installation process will fail or issue an error that it is not the correct install package.

    I don't think that the architecture of the Agent is the problem since Control-M for Database uses Microsofts API to run SSIS packages.

    This is why as part of the Control-M for Database installation, you are required to install SQL Server Integration Services as this will provide the required APIs for CTM to be able to run SSIS packages.

    It could be that the problem is with the SSIS Service installation? I don't have a way to check it right now but is it possible to install x86 SSIS Service on 64 bit platform? Maybe this is what you did and you need to install the 64bit version?

     

    If you are able to run a job, although it fails, try putting here some output of the logs, maybe it will help getting the root cause.

     

    Regards,

    WhiteLady

  • 8. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    Hi WhiteLady,

     

    Thanks for your Reply.

     

    i have installed 64bit version of Control-M Agent and DB module,  and  account has been verified.

     

    I am trying SSIS solution , currently SSIS job is running on the server with 32-bit mode in SQL server ( remember SQL server is 64 bit version)

     

    As you said Control-M for Database uses Microsofts API to run SSIS packages, Does CM has capability to run SSIS job on 32bite mode on 64-bit SQL Server.

     

    i have other SSIS job running on the same agent  with default mode ( 64-bit mode ) and it is running fine.

     

    below is the error when i run SSIS job from control-M

     

      ERROR: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.1 is not registered -- perhaps \ 

    no 64-bit provider is available.  Error code: 0x00000000.

    An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registe\

    red".

     

    I Guess SSIS Service installation has gone through.

     

    have you faced this kind of scenario

     

    Thanks

    Rashid

  • 9. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    WhiteLady

    Hi Rashid,

     

    Why are you running this package in 32 bit mode? If you change it to 64 the problem is gone?

    You write "i have other SSIS job running on the same agent  with default mode ( 64-bit mode ) and it is running fine." - Do you mean the CTM Agent or the SQL Agent?

    I am not familiar with this scenario, but to your question, the CM for DB is "blind" to the architecture of the SQL Server. It has no way of knowing if it's 32 or 64.

    I have asked you about the SSIS services installed on the CTM Agent side, did you verify if they are 32 or 64 bit?

    Are the CTM Agent and the SQL DB installed on the same machine? Reading your first comment may suggest that they are, so my advise is to try and install the Agent on a different host and try running the package.

    Where you able to run any SSIS package using CTM?

    Last, usually the best way to identify if a problem is with CTM is to try and run the SSIS package with dtexecui utility. So you should try and run the package with dtexecui first, and if it fails, try resolving the errors displayed.

    As long as a package fails to run with dtexecui/dtexec utility, it will also fail in CTM.

     

    Regards,

    WhiteLady

  • 10. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    Hi WhiteLady,

     

    This particular SSIS package needs to run only on 32 bit , since the data is pulled from 32-bit DB . Hence the SSIS job has to run on 32 bit mode . it is runing fine with help of SQL server agent on 32-bit mdoe . but when i run from control-M with CM DB it is error show in above

     

    CTMAGENT and CM are installed on 64bit and DB also on the same server ( SQL SERVER 64 bit )

     

    I am able to run SSIS job with CM DB by default mode (64 bit -mode ) through control-M it  is running fine.

     

    I am able to run problematic SSIS job with the help of 32bit dtexec utility from the command line.

     

    SSIS services running fine  version SQL Server Integration Services 10.0 is running fine.

     

    Thanks

  • 11. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    WhiteLady

    Hi Rashid,

     

    Maybe you found a limitation of CTM (probably Microsoft's API but doesn't really matter) where when installed on 64 bit, fails to run 32 bit packages.

    As I wrote, CTM for DB is not aware of the architecture so there is nothing you can do right now on the CTM side except for installing the Agent + CTM for DB + SSIS Services on a 32bit Windows system and try to schedule the SSIS package from there.

    unfortunately I do not have a similiar configuration to what you are using but if I do get my hands on such an environment, I'll try running your scenario.

     

    Regards,

    WhiteLady

  • 12. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    seadala@atd-us.com

    Hi Rashid,

     

    Did you get this resolved and run through control-M? I have the same issue too and looking for answer.

  • 13. Re: unable to run 32 bit SSIS package on 64-bit 2008 WIN server
    Mohamed Rashid

    hi

     

    No I couldnt , I am running with dtexec utility , let me know if you get any way out of this.

     

    Thanks