+ Reply to Thread
Results 1 to 6 of 6

Process cube task in SSIS package

  1. Process cube task in SSIS package

    Hi Folks,

    I created a SSIS package to process an AS 2005 cube (DB2 data source) via
    DTExec command within a batch job. The batch job always runs on a production
    SSIS server.

    I have a log file set in that SSIS package with two checked events OnError
    and OnTaskFailed. However, sometimes, the error message of processing cube
    task failed could not be written into the ssis log file, it just popped up a
    window on the SSIS server screen that I couldn't see. I am wondering if there
    is a way can capture all the error messages in the log file. Is this problem
    caused by SSIS or SSAS or anything else?

    Hope some of you can give me some hints!!
    Thanks in advance!

    Regards!
    Helen

  2. Re: Process cube task in SSIS package

    When executing through DTExec the errors should be logged through the
    log providers and should not appear througha popup. What does the popup
    say? You say you cannot see the popup so how do you know it is
    happening?

    --


    Allan Mitchell
    http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
    http://www.konesans.com



    "Helen" wrote in message
    news:B17B6AAA-3348-4FE5-A67E-619707E985AA@microsoft.com:

    > Hi Folks,
    >
    > I created a SSIS package to process an AS 2005 cube (DB2 data source) via
    > DTExec command within a batch job. The batch job always runs on a production
    > SSIS server.
    >
    > I have a log file set in that SSIS package with two checked events OnError
    > and OnTaskFailed. However, sometimes, the error message of processing cube
    > task failed could not be written into the ssis log file, it just popped up a
    > window on the SSIS server screen that I couldn't see. I am wondering if there
    > is a way can capture all the error messages in the log file. Is this problem
    > caused by SSIS or SSAS or anything else?
    >
    > Hope some of you can give me some hints!!
    > Thanks in advance!
    >
    > Regards!
    > Helen



  3. SSIS 2005 error in processing SSAS 2005 cube

    Hello Guys!

    I have created an SSIS package that process my cube every hour. However, I tried to look at the log files on the Job Monitor of SQL Database server and I found these errors:

    Started: 11:00:01 AM
    Error: 2008-04-10 11:00:04.57
    Code: 0xC020801E
    Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS" is an incorrect type. The type required is "FILE". The type available to the component is "MSOLAP90".
    End Error
    Error: 2008-04-10 11:00:04.59
    Code: 0xC020801E
    Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS" is an incorrect type. The type required is "FILE". The type available to the component is "MSOLAP90".
    End Error
    DTExec: The package execution returned DTSER_SUCCESS (0).
    Started: 11:00:01 AM
    Finished: 11:01:37 AM
    Elapsed: 96.168 seconds
    Microsoft (R) SQL Server Execute Package Utility
    Version 9.00.3042.00 for 32-bit
    Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

    I have tested the package in BIDS 2005 and it works fine but after I deployed it to the SQl Database server, the problem occurs. WHat do I need to do in order to resolve this?

    I tried searching the net for some answers but to no avail.

    Kindly help me with this please.

    Thanks in advance.

  4. Re: SSIS 2005 error in processing SSAS 2005 cube

    I've not experienced this sort of error myself but looking at the message it
    appears as though the SSIS logging is failing because it is using an OLAP
    connection rather than the file connection it is expecting.

    Are you using configurations? Reason I ask is that you say you only get this
    problem when you deploy to the server. Its possible that the configuration
    for that server is using an OLAP data provider in the connection string
    rather than a file connection, and this is why you're getting this
    behaviour.

    HTH

    --
    Phil

    http://www.clarity-integration.com
    http://www.phil-austin.blogspot.com

    "jd morales" wrote in message news:2008427224821ja_coolz@yahoo.com...
    > Hello Guys!
    >
    > I have created an SSIS package that process my cube every hour. However, I
    > tried to look at the log files on the Job Monitor of SQL Database server
    > and I found these errors:
    >
    > Started: 11:00:01 AM
    > Error: 2008-04-10 11:00:04.57
    > Code: 0xC020801E
    > Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    > Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS"
    > is an incorrect type. The type required is "FILE". The type available to
    > the component is "MSOLAP90".
    > End Error
    > Error: 2008-04-10 11:00:04.59
    > Code: 0xC020801E
    > Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    > Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS"
    > is an incorrect type. The type required is "FILE". The type available to
    > the component is "MSOLAP90".
    > End Error
    > DTExec: The package execution returned DTSER_SUCCESS (0).
    > Started: 11:00:01 AM
    > Finished: 11:01:37 AM
    > Elapsed: 96.168 seconds
    > Microsoft (R) SQL Server Execute Package Utility
    > Version 9.00.3042.00 for 32-bit
    > Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
    >
    > I have tested the package in BIDS 2005 and it works fine but after I
    > deployed it to the SQl Database server, the problem occurs. WHat do I need
    > to do in order to resolve this?
    >
    > I tried searching the net for some answers but to no avail.
    >
    > Kindly help me with this please.
    >
    > Thanks in advance.



  5. Re: SSIS 2005 error in processing SSAS 2005 cube

    have you found a solution for this? I'm getting same error!!

    "Phil" wrote:

    > I've not experienced this sort of error myself but looking at the message it
    > appears as though the SSIS logging is failing because it is using an OLAP
    > connection rather than the file connection it is expecting.
    >
    > Are you using configurations? Reason I ask is that you say you only get this
    > problem when you deploy to the server. Its possible that the configuration
    > for that server is using an OLAP data provider in the connection string
    > rather than a file connection, and this is why you're getting this
    > behaviour.
    >
    > HTH
    >
    > --
    > Phil
    >
    > http://www.clarity-integration.com
    > http://www.phil-austin.blogspot.com
    >
    > "jd morales" wrote in message news:2008427224821ja_coolz@yahoo.com...
    > > Hello Guys!
    > >
    > > I have created an SSIS package that process my cube every hour. However, I
    > > tried to look at the log files on the Job Monitor of SQL Database server
    > > and I found these errors:
    > >
    > > Started: 11:00:01 AM
    > > Error: 2008-04-10 11:00:04.57
    > > Code: 0xC020801E
    > > Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    > > Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS"
    > > is an incorrect type. The type required is "FILE". The type available to
    > > the component is "MSOLAP90".
    > > End Error
    > > Error: 2008-04-10 11:00:04.59
    > > Code: 0xC020801E
    > > Source: Package Log provider "{7B677755-3D89-41D9-A237-8BBA441C4019}"
    > > Description: The connection manager "CRM4RTM.Maynilad CRM Analyzer AS"
    > > is an incorrect type. The type required is "FILE". The type available to
    > > the component is "MSOLAP90".
    > > End Error
    > > DTExec: The package execution returned DTSER_SUCCESS (0).
    > > Started: 11:00:01 AM
    > > Finished: 11:01:37 AM
    > > Elapsed: 96.168 seconds
    > > Microsoft (R) SQL Server Execute Package Utility
    > > Version 9.00.3042.00 for 32-bit
    > > Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
    > >
    > > I have tested the package in BIDS 2005 and it works fine but after I
    > > deployed it to the SQl Database server, the problem occurs. WHat do I need
    > > to do in order to resolve this?
    > >
    > > I tried searching the net for some answers but to no avail.
    > >
    > > Kindly help me with this please.
    > >
    > > Thanks in advance.

    >


  6. The connection manager "..." is an incorrect type. Thetype required is "FILE".

    Hi! I got similar challenge today. It would imagine it may be connected with 64 bit version as when deployed to 32-bit works fine.

    It may be worth to mention that in my case although error still occurs on the Test and Production it does not prevent the package from the successful run!

    Ok then try the following:
    1. Run from command prompt DTExecUI.
    2. On General Tab select your package file (.dtsx) 3. On Configurations Tab select package configuration file (.dtsConfig).
    4. Go to last option "Command Line" copy the command
    5. Paste the command into windows command prompt add DTExec at the beginning of the command and run...

    Now check for an error messages. Hopefully error will not apear and there is something else missing. Hope this helps.

    Cheers
    Rob




+ Reply to Thread