Error while executing a Package in Parallel.

Hi All,
We are trying to execute a package in parallel. Our execution stopped while when the package is running for the sixth time. The error for that execution is as follows :
ODI-1241: Oracle Data Integrator tool execution fails.
Caused By: oracle.odi.runtime.agent.invocation.InvocationException: HTTP/1.1 500 Could not get JDBC Connection; nested exception is java.sql.SQLException: Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:271)
at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartScenario(InternalRemoteRuntimeAgentInvoker.java:149)
at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java:266)
at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:155)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3185)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:1414)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2785)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1818)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:559)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
.....Some more
Can anyone suggest your pointers on this.?
Regards.

It looks like you have exceeded the number of connections available for the datasource. Try checking your connection pool settings.

Similar Messages

  • Getting Error while Execute SSIS Package from Console Application

    Dear All,
    SSIS package working fine directly.
    I got following error while execute SSIS package from C# console application.
    The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
    Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
    in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
    OLE DB Destination failed validation and returned error code 0xC004800B.
    One or more component failed validation.
    There were errors during task validation.
    Code : 
       public static string RunDTSPackage()
                Package pkg;
                Application app;
                DTSExecResult pkgResults;
                Variables vars;
                app = new Application();
                pkg = app.LoadPackage(@"D:\WORK\Package.dtsx", null);
         Microsoft.SqlServer.Dts.Runtime.DTSExecResult results = pkg.Execute();
    I have recreate the application with again new connection in SSIS.
    Still not working, Please provide solution if any one have.
    DB : SQL Server 2008 R2
    Thanks and regards,
    Hardik Ramwani

    The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
    Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
    in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
    Are you sure that you are running the same package via .NET which works fine from Visual Studio?
    By reading error message, I can say that you have copied OLEDB task from another package OR you have deleted one OLEDB connection manager. Now when package is run this task tries to use the connection manager and not found thus throws error message.
    Open all OLEDB destination tasks and you find connection manager missing. Connection Manager name should be provided there
    Cheers,
    Vaibhav Chaudhari
    MCSA - SQL Server 2012

  • Error while executing SSIS package which contains Script component through SQL Server Agent Job

    Hello All,
    I have written one SSIS 2012 package which is fetching records from CSV and put it into staging DB and from staging DB , using SSIS script component task, I am inserting data into Dynamics CRM. So far it is working fine when
    I manually execute SSIS package.
    but when I run the SSIS package using SQL server agent job, I encounter below error. After seeing below error at step "Insert TLM Headers Script Component " I understand that it is failing at script component which I have used in SSIS package,
    but I am not sure what is the cause behind that? please advise.
    Error:
    Executed as user: domain\user account. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.5556.0 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  1:21:41 PM  Error: 2015-02-25
    13:21:45.94     Code: 0xC0047062     Source: Insert TLM Headers Script Component [205]     Description: System.ServiceModel.FaultException: The server was unable to process the request due to an internal
    error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to
    the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.    Server stack trace:      at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message
    reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)    
    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
    methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception
    e)     at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)     at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100
    wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)  End Error  Error: 2015-02-25 13:21:45.94     Code: 0xC0047022     Source: Insert TLM Headers SSIS.Pipeline    
    Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "Script Component" (205) failed with error code 0x80131501 while processing input "Input 0" (215). The identified component returned an error
    from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the failure.  End Error 
    DTExec: The package execution returned DTSER_FAILURE (1).  Started:  1:21:41 PM  Finished: 1:21:45 PM  Elapsed:  4.009 seconds.  The package execution failed.  The step failed.
    Thanks
    Pankaj

    domain\user account has not proper rights
    That being said, often SSIS jobs require a proxy to be runnable and this is how you make one up
    http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
    Arthur
    MyBlog
    Twitter

  • Error while executing a package in ODI

    Hi,
    I am new to Oracle technology and when i am trying to execute one package through Oracle Data Integrator i am getting the below error. Even when i am trying to execute the procedure 'GENERATE_NAT_KEY' i am getting the error
    ODI-1228: Task Generate Natural Key (Procedure) fails on the target ORACLE connection ORACLE_OII.
    Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier
    ORA-06512: at "OII_ST.GENERATE_NAT_KEY", line 65
    ORA-06512: at line 2
    I am not able to figure out the issue. Can any one help me in this regards.

    Hi;
    You have to login https://support.oracle.com/CSP/ui/flash.html and you have to CSI account.
    This site is oracle site for tech. documents for can rise SR etc.. for more details please check Re: Installing Oracle Database 10.2.0.4
    you need to customer support identifier which is called CSI for can login metalink(https://support.oracle.com/CSP/ui/flash.html)
    If you dont have metalink account there is no way to see that doc.
    Pretty simple process:
    1) You purchase a perpetual or term license from Oracle;
    2) At the beginning of the period, during the valid term you purchase
    Support for the period (1 year);
    3) Oracle sends you the CSI.
    Easy to do at http://store.oracle.com armed with a credit card.
    Regard
    Helios

  • Error while executing SSIS Package after upgrading the Oracle Client

    Hello,
    I am running to the below error after we upgraded the Oracle client to 11g from 10g. The source of the Data is Oracle database . Looked online but each error is pointing towards different route, Confused here any help is very much appreciated. Have to say
    I am not a pro with SSIS.
    SSIS package "Bentek_ISO_Package (2).dtsx" starting.
    Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
    Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
    Warning: 0x80049304 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available.  To resolve, run this package as an administrator,
    or on the system's console.
    Information: 0x40043006 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
    Information: 0x40043007 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
    Error: 0xC0202009 at Temp_tbl Injection Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E14.
    An OLE DB record is available.  Source: "OraOLEDB"  Hresult: 0x80040E14  Description: "ORA-12801: error signaled in parallel query server P183, instance *****:qrmgmt2 (2)
    ORA-01861: literal does not match format string".
    An OLE DB record is available.  Source: "OraOLEDB"  Hresult: 0x80004005  Description: "ORA-12801: error signaled in parallel query server P183, instance ****:qrmgmt2 (2)
    ORA-01861: literal does not match format string".
    Error: 0xC004701A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.
    Information: 0x4004300B at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: "component "OLE DB Destination" (52)" wrote 0 rows.
    Information: 0x40043009 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
    Task failed: Temp_tbl Injection Data Flow Task
    Warning: 0x80019002 at *******: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
    the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
    SSIS package "****** (2).dtsx" finished: Failure.

    Do you have any Date conversion functions in your Oracle datetime fields? I did run into a similar issue when we upgraded the oracle client and the provider started to decipher the metadata of the date columns. The SSIS metadata conversion for the date
    columns yielded dates that were not valid. I had to update my queries to use the TO_CHAR conversion to bring it out as a string and then save it to the date field.
    TO_CHAR (DATE, 'MM/DD/YYYY HH24:MI:SS')
    Regards, Dinesh

  • Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

    Hi,
    We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
    Error: 4014, Severity:20, State: 11.   A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
    SQL Server Data Tools and SQL Server Database Engine reside on the same server.
    We tried the following:
    Disabling TCP Chimney Offload
    Installed Windows Server 2008 SP1
    Splitting our SSIS code into multiple steps so it is not all one large continuous operation
    The error occurs during a BulkDataLoad task.
    Other options we are investigating with the engineering team (out-sourced, so delayed responses):
    Firewall configurations (everything is local, so this should not make a difference)
    Disabling the anti-virus scanner
    Are there other things we can try?
    Any insight is greatly appreciated.
    Thanks!

    Hi HenryKwan,
    Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
    Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
    Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
    Set "RetainSameConnection" Property to FALSE on the all the connection managers.
    Reference:
    https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
    If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SQL SERVER - Error while executing SSIS package on specific environment : Connection manager - The specified module could not be found

    I have deployed my SSIS packages on SQL 2008 server.
    I have a .bat file which will invoke these packages and also the bat file is placed in the server where the SSIS packages are deployed.
    Scenario 1:
    I double clicked on the bat file to invoke the SSIS packages and ; this executed successfully
    Scenario 2:
    I have used the IBM Tivoli work scheduler(TWS)  to invoke the bat file which in tern will invoke the ssis packges; 
    but when i do this i am getting the below error
     Code: 0x8007007E
       Source: SSIS_Master_Event_Data_Transfer Connection manager "Config DB"
       Description: The specified module could not be found.
    Config BD is a connection manager which will get the connection string from the config file of the SSIS package.
    Please help me to resolve this issue.
    Regards,
    Prakash

    Check you TWS jobmanrc.cmd configuration file.   You may need to add a PATH environment variable in that file that includes your SQL Server file locations.   When TWS jobs are executed, they may not be executing with the same
    PATH variable as when you execute the SSIS outside of TWS.

  • Gettng Error while executing the procedure(oracle 10.2.0.3.0)

    Hi all,
    I am getting following error While executing the package .
        PLS-00103: Encountered the symbol "Truncate" when expecting one of
             the following:
             * & = - + ; < / > at in is mod remainder not rem return
             returning <an exponent (**)> <> or != or ~= >= <= <> and or
             like LIKE2_ LIKE4_ LIKEC_ between into using || multiset bulk
             member SUBMULTISET_I have written follwing query in the package body.
    EXECUTE IMMEDIATE 'TRUNCATE TABLE FORT ';
    EXECUTE IMMEDIATE '
         INSERT INTO FORT (CID,CODE,DESC,SCODE,SES,T_DT,SDN,LANG)
         SELECT
           SERVICES.CID                                                     CID,
           PROFILE.FUCODE                                               CODE,
           TO_DATE(SUBSTR(SERVICES.STAT_CHNG,-7,6),'YYMMDD')   T_DT,
           PHOR.NUM                                                               SDN,
           C_ALL.cLANGUAGE                                      LANG
         FROM
          SERVICES      .....Please give me the solution for this .
    Thank y ou
    Edited by: user636482 on Apr 10, 2009 1:08 AM

    I am getting following errors if I gave " ' " after not null.
    LINE/COL ERROR
    42/8     PLS-00103: Encountered the symbol "AND" when expecting one of the
             following:
             begin case declare end exception exit for goto if loop mod
             null pragma raise return select update while with
             <an identifier> <a double-quoted delimited-identifier>
             <a bind variable> << close current delete fetch lock insert
             open rollback savepoint set sql execute commit forall merge
             pipe
    42/56    PLS-00103: Encountered the symbol "A" when expecting one of the
             following:
    LINE/COL ERROR
             ) , * & | = - + < / > at in is mod remainder not rem => ..
             <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
             LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
             The symbol ", was inserted before "A" to continue.
    42/74    PLS-00103: Encountered the symbol "D" when expecting one of the
             following:
             * & - + ; / at mod remainder rem return returning
             <an exponent (**)> and or || multiset
             The symbol "* was inserted before "D" to continue.
    LINE/COL ERROR
    45/6     PLS-00103: Encountered the symbol "COMMIT"
    52/3     PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    85/8     PLS-00103: Encountered the symbol "AND" when expecting one of the
             following:
             begin case declare end exception exit for goto if loop mod
             null pragma raise return select update while with
    LINE/COL ERROR
             <an identifier> <a double-quoted delimited-identifier>
             <a bind variable> << close current delete fetch lock insert
             open rollback savepoint set sql execute commit forall merge
             pipe
    85/56    PLS-00103: Encountered the symbol "A" when expecting one of the
             following:
             ) , * & | = - + < / > at in is mod remainder not rem => ..
             <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
             LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
             The symbol ", was inserted before "A" to continue.
    LINE/COL ERROR
    85/74    PLS-00103: Encountered the symbol "D" when expecting one of the
             following:
             * & - + ; / at mod remainder rem return returning
             <an exponent (**)> and or || multiset
             The symbol "* was inserted before "D" to continue.
    88/8     PLS-00103: Encountered the symbol "COMMIT"
    95/3     PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
    LINE/COL ERROR
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    133/3    PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    169/3    PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:with out adding " ' " I am getting the previous error which I mentioned in Previous thread(TRUNCATE)
    Thank you

  • We are facing error while executing Bex report.

    Hi Gurus:
    We are facing error while executing Bex report.
    Messge :                                                                          
    u201CQuery 0: Runtime error program state check for conversation 05284411 / CP  with parallel processing via RFC
    Message no. DBMAN428u201D
    The query is based upon Multiprovider (based upon 2 basic cubes).
    Both cubes are partitioned by   info object 0CALMONTH, (valid range - 01.2005 - 012.2010).
    Those cubes are not containing any non-cumulative key figures and Service package level for  SAP NetWeaver BI 7.0 is  u2018SAPKW70012u2019.
    I have checked those cubes in RSRV and carry out following steps:
    "All Elementary Tests -> Transaction Data" and execute the repair "Consistency of the Time Dimension for an Info Cube"
    I have found system inconsistency like u201CRecord with the DIMID 2 contains non-fitting time characteristics u201C
    Detail ERROR:
    Record with the DIMID 2 contains non-fitting time characteristics
    Message no. RSCV053Diagnosis
    The data record of the time dimension table with the described DIMID contains values for time characteristics that do not fit together.
    I have found the u2018 Note 1130450 - Query displays error DBMAN 284; RSRV: Time dimension checku2019  for this but still not sure this will work or not .
    I tested this in dev server , didn't feel useful.
    Could you please let us know what to correct this error.
    Anwser will be rewared.
    Regards,

    >
    Surendra Pande wrote:
    > Anwser will be rewared.
    > Regards,
    Go read the RULES of these forums.

  • Error while executing DTP

    Hi gurus,
    Iam trying to extract the data from r/3 using generic extractor the data is loaded into PSA sucessfully, but iam getting following errors while executing DTP.
    1.An error occurred while executing a transformation rule:
    The exact error message is:
    The argument 'EA' cannot be interpreted as a number
    The error was triggered at the following point in the program
    GP4D35STLXQI3SHIVNQC2FSJ7MB 791
    2.The data record was filtered out because data records with the same key
    have already been filtered out in the current step for other reasons and
    the current update is non-commutative (for example, MOVE). This means
    that data records cannot be exchanged on the basis of the semantic key.
    Please guide me accordingly.
    Regards
    Amar.

    Hi
    While mapping the Qty Fields it is must to add UOM to the Qty Fields and map it with relevant Info Objects.
    The Semantic Keys defined at DTP are also has some issues, try to give a dummy key figure if you are using DSO in the data flow as the DSO has the Overwrite mode.
    (Choose  Semantic Groups to specify how you want to build the data packages that are read from the source (DataSource or InfoProvider). To do this, define key fields. Data records that have the same key are combined in a single data package. This setting is only relevant for DataStore objects with data fields that are overwritten. This setting also defines the key fields for the error stack. By defining the key for the error stack, you ensure that the data can be updated in the target in the correct order once the incorrect data records have been corrected.)
    Hope it helps and clear

  • Error while executing the rule session

    Hi, I am using Oracle Business Rules Engine 10.1.3.3.0.I am developing rules using XML Facts.I am using a complex type array schema and binding it to define XML facts.Earlier the depth of the schema is 1 and it worked fine,now our schema's depth is 2 and while binding this schema is also working fine.The sample structure of the present schema I am binding is
    <xsd:schema>
    <xsd:element name = 'ruleRepository' type = 'RuleRepositoryType'/>
    <xsd:complexType name='RuleRepositoryType'>
    <xsd:sequence>
    <xsd:element ='ruleFacts' type='RuleFactsType' minOccurs='0' maxOccurs='unbounded'/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name='RuleFactsType'>
    <xsd:sequence>
    <xsd:element name='fact1' type='xsd:string'/>
    <xsd:element name='fact2' type='xsd:string'/>
    <xsd:element name='fact3' type='xsd:string'/>
    <xsd:element name='fact4' type='Fact4' minOccurs='0' maxOccurs='unbounded'/>
    <xsd:sequence/>
    </xsd:complexType>
    <xsd:complexType name='Fact4'>
    <xsd:sequence>
    <xsd:element name='element1' type='xsd:string'/>
    <xsd:element name='element2' type='xsd:string'/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Earlier I have binded the similar schema as above but without 'fact4'.It went well and the rules were executing fine.
    However when I am trying to bind a similar schema like the above one, its binding fine but when executing from the BPEL Process,its giving errors like,
    "Error Caching Decision Services metadata,fact3 is undefined in DM,line6,Column 12",
    Please note that I am using fact1 and fact2 only for defining the rules , I am niether using fact3 which is a simple type nor fact4 which is a complex type.
    I have asserted Package.RuleRepositoryType in the definitions of the rule author.I have tried with different combinations of assertions but no one worked.
    The above error(
    "Error Caching Decision Services metadata,fact3 is undefined in DM,line6,Column 12") is coming for the first run of the decision service only,in the next runs its giving another error,which is like
    <2008-04-10 07:52:30,772> <ERROR> <default.collaxa.cube.services> <::> ORABPEL-36333
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::>
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> Error while executing the rule session.
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> The rule session {0} failed to execute.
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::>
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:251)
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.impl.DecisionServiceImpl.process(DecisionServiceImpl.java:1385)
    <2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.impl.DecisionServiceImpl.assertExecuteWatchStateless(DecisionServiceImpl.java:546)
    <2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.invoke_assertExecuteWatchStateless(BookOrderDecisionSOAPBinding_Tie.java:162)
    <2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.processingHook(BookOrderDecisionSOAPBinding_Tie.java:457)
    <2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
    <2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
    <2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
    <2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    <2008-04-10 07:52:30,801> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at java.lang.Thread.run(Thread.java:595)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> Caused by: java.lang.NullPointerException
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.RuleSessionPool.getSession(RuleSessionPool.java:463)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:224)
    <2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> ... 26 more
    <2008-04-10 07:52:30,803> <ERROR> <oracle.bpel.services> <::>
    java.lang.NullPointerException
    at oracle.bpel.services.rules.rpi.oracle.RuleSessionPool.getSession(RuleSessionPool.java:463)
    at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:224)
    at oracle.bpel.services.rules.impl.DecisionServiceImpl.process(DecisionServiceImpl.java:1385)
    at oracle.bpel.services.rules.impl.DecisionServiceImpl.assertExecuteWatchStateless(DecisionServiceImpl.java:546)
    at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.invoke_assertExecuteWatchStateless(BookOrderDecisionSOAPBinding_Tie.java:162)
    at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.processingHook(BookOrderDecisionSOAPBinding_Tie.java:457)
    at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
    at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
    at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
    at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    08/04/10 07:52:30 pFaultMessage is org.collaxa.thirdparty.apache.wsif.base.WSIFDefaultMessage@6e0e5f name:operationErroredFault
    08/04/10 07:52:30 QName string is operationErroredFault
    where 'BookOrderDecision' is the name of the decision service I am using in BPEL.
    I dont understand why I am getting two errors for the same BPEL Process.
    Kindly help me in this problem.I am stuck with this for about a week but could not get to the solution.
    Thanks in advance.
    Regards,
    Venkat.

    Hi Venkat,
    Whenever you do schema changes, you need to go through the cycle of
    re-importing the XML schema in the rule repository, re-create the decision
    service partnerlink, re-deploy the decision service.
    I suspect you have maybe imported the entire XML fact type model (with fact3 and
    fact4) instead of just fact1 and fact2 (might want to check in rule author).
    So even if you don't use fact3 and fact4 in decision service, they are part of the rules
    datamodel.
    Regards,
    Ralf

  • Fatal error while executing the DQS installer on SQL Server 2014

    Hi all.
    I am receiving the following error when attempting to install DQS on the following platform:
    Windows Server 2012
    Microsoft SQL Server 2014 - 12.0.2000.8 (X64)   Feb 20 2014 20:04:26   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    (no entries in event viewer)
    Error is:
    [4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
    Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
    to an instance of an object.
       at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
       at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
       at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
       --- End of inner exception stack trace ---
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
       at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
       at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
    Thanks for any advice you can give.
    Full log below:
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.
    [4/15/2015 7:58:20 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
    [4/15/2015 7:58:20 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
    [4/15/2015 7:58:20 AM] Using instance: DW01, catalog: DQS.
    [4/15/2015 7:58:20 AM] Executing action: Validate collation argument.
    [4/15/2015 7:58:20 AM] Action 'Validate collation argument' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Check whether system reboot is pending.
    [4/15/2015 7:58:20 AM] Action 'Check whether system reboot is pending' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Create data quality event source.
    [4/15/2015 7:58:20 AM] Action 'Create data quality event source' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Request Database Master Key password from user..
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.
    [4/15/2015 8:39:59 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
    [4/15/2015 8:39:59 AM] Parsing DqsInstaller command line arguments.
    [4/15/2015 8:39:59 AM] Setting the catalog to default value: DQS
    [4/15/2015 8:39:59 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
    [4/15/2015 8:39:59 AM] Using instance: DEV01, catalog: DQS.
    [4/15/2015 8:39:59 AM] Executing action: Validate collation argument.
    [4/15/2015 8:39:59 AM] Action 'Validate collation argument' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Check whether system reboot is pending.
    [4/15/2015 8:39:59 AM] Action 'Check whether system reboot is pending' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Create data quality event source.
    [4/15/2015 8:39:59 AM] Action 'Create data quality event source' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Request Database Master Key password from user..
    [4/15/2015 8:41:05 AM] Action 'Request Database Master Key password from user.' finished successfully.
    [4/15/2015 8:41:05 AM] Executing action: Approve removal of data quality services previous schema.
    [4/15/2015 8:41:05 AM] Action 'Approve removal of data quality services previous schema' finished successfully.
    [4/15/2015 8:41:05 AM] Executing action: Load Installation Scripts.
    [4/15/2015 8:41:05 AM] Extracting script to: C:\Users\SqlServiceAcct\AppData\Local\Temp\3mo2vwbu.xch
    [4/15/2015 8:41:06 AM] Extracting script: db\create_core_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\create_logic_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\create_transient_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\static_data.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\drop_dq_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\db_version.sql
    [4/15/2015 8:41:06 AM] Extracting script: helper\DeleteSchemaDs.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\create_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_tables.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_database_properties.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\master_create.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\master_recreate.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies_tsql.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_dq_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\create_service_broker_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_service_broker_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_single_user.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_multi_user.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\upgrade_all_versions.sql
    [4/15/2015 8:41:06 AM] Extracting script: recreate_schema.bat
    [4/15/2015 8:41:06 AM] Extracting script: upgrade_schema.bat
    [4/15/2015 8:41:06 AM] Extracting script: upgrade_version_tables.bat
    [4/15/2015 8:41:06 AM] Extracting script: drop_databases.cmd
    [4/15/2015 8:41:06 AM] Extracting script: register_dlls.cmd
    [4/15/2015 8:41:06 AM] Extracting script: unregister_dlls.cmd
    [4/15/2015 8:41:06 AM] Extracting script: assembly_paths_retail.txt
    [4/15/2015 8:41:06 AM] Extracting script: DQS_Data.dqs
    [4/15/2015 8:41:06 AM] Extracting script: DefaultKbs.xml
    [4/15/2015 8:41:06 AM] Total scripts extracted: 31
    [4/15/2015 8:41:06 AM] Action 'Load Installation Scripts' finished successfully.
    [4/15/2015 8:41:06 AM] Executing action: Create data quality schema.
    [4/15/2015 8:41:06 AM] Script: 'recreate_schema.bat CMTSQLSVR04\DEV01 DQS SQL_Latin1_General_CP1_CI_AS'
    [4/15/2015 8:41:06 AM] .  Trying to connect using Windows Authentication and db name...
    [4/15/2015 8:41:06 AM] Run create_databases.sql to create Data Quality Service databases if they do not exist.
    [4/15/2015 8:41:07 AM] 
    [4/15/2015 8:41:07 AM]  --> Running File: create_databases.sql
    [4/15/2015 8:41:07 AM] ---[ Creating databases ]---
    [4/15/2015 8:41:07 AM] Changed database context to 'master'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_dq_database.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Data Quality Databases ]---
    [4/15/2015 8:41:10 AM] Creating DQS databases (DQS_MAIN, DQS_PROJECTS, DQS_STAGING_DATA)...
    [4/15/2015 8:41:10 AM] Configuring DQS databases
    [4/15/2015 8:41:10 AM] Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Creating Master Key for database DQS_MAIN...
    [4/15/2015 8:41:10 AM] Creating Module Signing Certificate for database DQS_MAIN...
    [4/15/2015 8:41:10 AM] Exporting Certificate from DQS_MAIN
    [4/15/2015 8:41:10 AM] Importing Certificate into DQS_PROJECTS
    [4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Creating DQS roles
    [4/15/2015 8:41:10 AM] Run master_recreate.sql to recreate Data Quality Service Main and Projects Databases and drop all tables including known temporary tables.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running master_recreate.sql
    [4/15/2015 8:41:10 AM] ---[ Recreate DQS Main and Projects Databases ]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_STAGING_DATA'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_all_tables.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Symmetric Keys ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Certificates ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all FK constraints ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all views ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all tables and synonyms ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all database triggers ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all stored procedures in Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all types in Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_all_tables.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Symmetric Keys ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Certificates ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all FK constraints ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all views ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all tables and synonyms ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all database triggers ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all stored procedures in Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all types in Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:11 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running master_create.sql
    [4/15/2015 8:41:11 AM] ---[ Creating and Populating Main DQS DB ]---
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_STAGING_DATA'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: create_core_db_objects.sql
    [4/15/2015 8:41:11 AM] ---[  Creating Certificates  ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM] ---[  Creating Symmetric Keys  ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM] ---[  Creating Tables  ]---
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEST   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEST2   
    [4/15/2015 8:41:11 AM] Creating Table:     A_FLOW   
    [4/15/2015 8:41:11 AM] Creating Table:     A_FLOW_ANSWER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_EXECUTION_UNIT
    [4/15/2015 8:41:11 AM] Creating Table:     A_CODE_GROUP   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CODE_MEMBER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CONFIGURATION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PROCESS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SERVICE_BROKER_TASK   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE_AUDIT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE_ACTIVITY   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PROFILING_ACTIVITY_ARCHIVE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CLIENT_SESSION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_PROVIDER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_PROVIDER_SCHEMA   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE_SUGGESTION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE_SUGGESTION_PARSED   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_AUDIT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_IMPORTED_PROJECT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SPELLER_DICTIONARY_VALUE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SPECIAL_CHARACTER_RULE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PERSISTENT_CACHE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_OBJECTS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_FOREIGN_KEYS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_COLUMNS   
    [4/15/2015 8:41:11 AM] ---[ Creating Views ]---
    [4/15/2015 8:41:11 AM] Creating View:      V_A_FLOW
    [4/15/2015 8:41:11 AM] Creating View:      V_A_KNOWLEDGEBASE
    [4/15/2015 8:41:11 AM] Creating View:      V_A_KNOWLEDGEBASE_AUDIT
    [4/15/2015 8:41:11 AM] Creating View:     V_A_REFERENCE_DATA_PROVIDER   
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: static_data.sql
    [4/15/2015 8:41:11 AM] ---[ Inserting Data ]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Cleansing configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Association configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert DataValueService configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Association rules configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert IndexService configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Knowledgebase configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Notification configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Interactive Cleansing configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert client paging configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert client process sampling configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Matching configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Profiling configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Process configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[FileStorageManager configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[ImportExportManager configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data Add provider]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data Add provider schema]---
    [4/15/2015 8:41:11 AM] ---[Add Special characters for term normalization]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: db_version.sql
    [4/15/2015 8:41:11 AM] ---[ Running version related work ]---
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_INFO   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_UPGRADE_SCRIPTS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_UPGADE_SCRIPT_PATH   
    [4/15/2015 8:41:11 AM] Creating view:     V_DB_VERSION 
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version information]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION in PROJECTS database 
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] Action 'Create data quality schema' finished successfully.
    [4/15/2015 8:41:11 AM] Executing action: Register data quality assemblies and stored procedures.
    [4/15/2015 8:41:11 AM] Script: 'register_dlls.cmd CMTSQLSVR04\DEV01 DQS'
    [4/15/2015 8:41:12 AM] .  Trying to connect using Windows Authentication and db name...
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running File: drop_all_assemblies.sql
    [4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Executable Objects ]---
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Types
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Assemblies
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Schemas
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all CLR Assemblies
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop DQ startup stored procedure DQInitDQS_MAIN
    [4/15/2015 8:41:12 AM] Changed database context to 'master'.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running File: drop_service_broker_objects.sql
    [4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Service Broker Objects ]---
    [4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Services.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Queues.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Contracts.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Messages.
    [4/15/2015 8:41:12 AM] Completed - Service Broker objects dropped.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running register_assemblies.sql
    [4/15/2015 8:41:12 AM] ---[ Registering Assemblies ]---
    [4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Registering Assemblies
    [4/15/2015 8:41:12 AM]      The following Warnings are benign to DQSInstaller and may be ignored.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]      * Register .NET dependency assemblies
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.management, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'smdiagnostics, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.windows.forms, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'accessibility, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization.formatters.soap, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the
    SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.jscript, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:26 AM] Warning: The Microsoft .NET Framework assembly 'system.management.instrumentation, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.messaging, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.enterpriseservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.remoting, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.framework, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.xaml, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.caching, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.utilities.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices.protocols, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web.regularexpressions, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.serviceprocess, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM]      * Register Microsoft.Practices assemblies
    [4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.csharp, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'system.dynamic, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:47 AM] 
    [4/15/2015 8:41:47 AM]      The preceding Warnings are benign to DQSInstaller and may be ignored.
    [4/15/2015 8:41:48 AM] 
    [4/15/2015 8:41:48 AM]  --> Running register_dq_assemblies.sql
    [4/15/2015 8:41:48 AM] ---[  Registering Data Quality assemblies ]---
    [4/15/2015 8:41:49 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.infra, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:50 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.core, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.dataservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.referencedata, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.index, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.associationrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:53 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.datavalueservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.domainrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.cleansing, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.association, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.flow, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:56 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.matching, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:57 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:57 AM] Resource file was not copied
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]  --> Running register_assemblies_tsql.sql
    [4/15/2015 8:41:57 AM] ---[ Registering Assemblies for TSQL]---
    [4/15/2015 8:41:57 AM] Changed database context to 'master'.
    [4/15/2015 8:41:57 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Clear the Code Member Table A_CODE_MEMBER.
    [4/15/2015 8:41:57 AM]
    [4/15/2015 8:41:57 AM] (0 rows affected)
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Clear the Code Group Table A_CODE_GROUP.
    [4/15/2015 8:41:57 AM]
    [4/15/2015 8:41:57 AM] (0 rows affected)
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Register assemblies T-SQL executable objects
    [4/15/2015 8:41:57 AM]         - Creating assemblies T-SQL registeration stored procedure.
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Creating the internal_core schema
    [4/15/2015 8:41:57 AM]         - Registering Microsoft.Ssdqs.Infra T-SQL executable objects.
    [4/15/2015 8:42:05 AM]         - Registering Microsoft.Ssdqs.Core T-SQL executable objects.
    [4/15/2015 8:42:11 AM]         - Registering Microsoft.Ssdqs.DataService T-SQL executable objects.
    [4/15/2015 8:42:16 AM]         - Registering Microsoft.Ssdqs.ReferenceData T-SQL executable objects.
    [4/15/2015 8:42:21 AM]         - Registering Microsoft.Ssdqs.Index T-SQL executable objects.
    [4/15/2015 8:42:26 AM]         - Registering Microsoft.Ssdqs.Cleansing T-SQL executable objects.
    [4/15/2015 8:42:32 AM]         - Registering Microsoft.Ssdqs.Association T-SQL executable objects.
    [4/15/2015 8:42:37 AM]         - Registering Microsoft.Ssdqs.Flow T-SQL executable objects.
    [4/15/2015 8:42:42 AM]         - Registering Microsoft.Ssdqs T-SQL executable objects.
    [4/15/2015 8:42:51 AM]         - Registering Microsoft.Ssdqs.DataValueService T-SQL executable objects.
    [4/15/2015 8:42:56 AM]         - Registering Microsoft.Ssdqs.DomainRules T-SQL executable objects.
    [4/15/2015 8:43:01 AM]         - Registering Microsoft.Ssdqs.AssociationRules T-SQL executable objects.
    [4/15/2015 8:43:06 AM]         - Registering Microsoft.Ssdqs.Matching T-SQL executable objects.
    [4/15/2015 8:43:12 AM]         - Creating refresh assemblies stored procedure.
    [4/15/2015 8:43:12 AM] Changed database context to 'master'.
    [4/15/2015 8:43:12 AM]         - Creating refresh assemblies helper linked server.
    [4/15/2015 8:43:12 AM]         - Creating and registering [dbo].[DQInitDQS_MAIN] (calls internal_core.InitServer) as startup stored procedure.
    [4/15/2015 8:43:12 AM] 
    [4/15/2015 8:43:12 AM]  --> Running File: create_service_broker_objects.sql
    [4/15/2015 8:43:12 AM] ---[ Registering Service Broker Objects ]---
    [4/15/2015 8:43:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:43:12 AM]         - Creating SB dispatcher stored procedure, messages and contract
    [4/15/2015 8:43:13 AM]         - Creating parallel execution SB queues and services
    [4/15/2015 8:43:13 AM]         - Creating calibration SB queues and services
    [4/15/2015 8:43:13 AM]         - Creating parallel calibration SB queues and services
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM] Successfully registered all assemblies.
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM] Action 'Register data quality assemblies and stored procedures' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Set product version property.
    [4/15/2015 8:43:13 AM] Action 'Set product version property' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Create MDS user (if MDS login exists).
    [4/15/2015 8:43:13 AM] Action 'Create MDS user (if MDS login exists)' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Load out of the box data.
    [4/15/2015 8:43:22 AM] Started loading knowledgebase 'DQS Data'
    [4/15/2015 8:45:04 AM] Starting installation rollback...
    [4/15/2015 8:45:04 AM] Installation rollback completed successfully.
    [4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
    Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
    to an instance of an object.
       at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
       at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
       at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
       --- End of inner exception stack trace ---
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
       at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
       at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.

    Thank you for the quick response.
    Unfortunately running cmd as admin had no effect on the result. Same exact error.
    After the rollback indicated in the log above, only the DQS_STAGING_DATA database remains in the sql server instance.

  • ERROR WHILE MIGRATING SSIS PACKAGE FROM DEVELOPMENT TO PRODUCTION IN EXECUTION

    HI,
    I have a problem while executing the package after migrating from DEVELOPMENT to PRODUCTION.
    We have two SQL database connections DEVMIDDLEWARE and PRODMIDDLEWARE for dev and prod respectively. When we have created package in development we have used DEVMIDDLEWARE and we have credentials in CONFIG file of that package and executed sucessfully. When
    we migrated this same package to PRODUCTION when have given credentials of PRODMIDDLEWARE in CONFIG FILE of this package we are getting error as below
    "Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic
    error. Verify that the correct key is available.  End Error  Error: 2014-10-28 07:41:44.24     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node
    "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. 
    End Error  Error: 2014-10-28 07:41:44.85     Code: 0xC0202009     Source: Package Connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware"     Description: SSIS Error Code DTS_E_OLEDBERROR. 
    An OLE DB error has occurred. Error code: 0x80040E4D.  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80040E4D  Description: "Login failed for user 'devmiddleware'.". 
    End Error  Error: 2014-10-28 07:41:44.85     Code: 0xC020801C     Source: Package Log provider "SSIS log provider for SQL Server"     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. 
    The AcquireConnection method call to the connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method
    call failed.  COM error object information is available.  Source: "Package"  error code: 0xC0202009  Description: "SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.  An OLE
    DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80040E4D  Description: "Login failed for user 'devmiddleware'.".  ".  End Error  Error: 2014-10-28 07:41:44.98    
    Code: 0xC0202009     Source: Package Connection manager "AGRDB01.abwr66"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.  An OLE DB record
    is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80040E4D  Description: "Login failed for user 'CC\epsdbuser'.".  End Error  Error: 2014-10-28 07:41:44.98     Code:
    0xC020801C     Source: Data Flow Task OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "AGRDB01.abwr66"
    failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error  Error: 2014-10-28 07:41:44.99     Code: 0xC0047017    
    Source: Data Flow Task SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.  End Error  Error: 2014-10-28 07:41:44.99     Code: 0xC004700C    
    Source: Data Flow Task SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2014-10-28 07:41:45.00     Code: 0xC0024107     Source: Data Flow Task     
    Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  07:41:44  Finished: 07:41:45  Elapsed:  0.859 seconds.  The package execution failed. 
    The step failed."
    Can anyone help for this error.
    Many thanx in Advance

    Hi Babloo,
    According to the error message, the package may have failed are as follows:
    The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
    The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
    The package may not run in the following scenarios:
    The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
    decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
    File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
    that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
    References:
    SSIS package does not run when called from a SQL Server Agent job step
    Run an SSIS Package Under a Different Account
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Error while running SSIS package from Integration service or via Job

    Hi All,
    I encounter the below error while running SSIS Package from Job or integration service. However on execution completes success fully while running from data tools. The issue occurs after migration to 2012 from 2oo5 dtsx. PFB the error.
    SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on OLE DB Source returned error code 0xC02020C4.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by
    the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.
    A buffer failed while allocating 10485760 bytes.
    The system reports 26 percent memory load. There are 206110765056 bytes of physical memory with 150503776256 bytes.
    free. There are 2147352576 bytes of virtual memory with 185106432 bytes free. The paging file has 208256339968 bytes with 145642921984 bytes free.
    The package also runs successfully from other servers. This happens only in one of our server.seems like issue with some sql configuration.

    Hi ,
    Are you running using SQL Agent Job and Data tools on same server or different?
    If it is executing fine using Data tools and failing with Job it might be User credentials issue.Try
    to run Job with your credentials by using proxy .
    Regards,
    Prathy
    Prathy K

  • Error while executing the CKMLCP (Actual Costing) Transaction

    Hi Expert,
    I am getting the following Error while executing the CKMLCP (Actual Costing) Transaction through my User ID in system. If we execute the same transaction  with other user id then there is no Error. same role is assign to both user. Try to check SU53 screen shot but it show no error
    See the below error for referance:-
    Internal error in program SAPLCKML_RUN_COCKPIT_ACT
    Message no. CKMLRUN004
    Diagnosis
    An unexpected situation has appeared in program SAPLCKML_RUN_COCKPIT_ACT.
    The problem has to do with a program error - the indirect result of a program error or an inconsistency in Customizing.
    System Response
    Processing had to be terminated.
    Procedure
    Inform your system administrator
    Thanks
    Dinesh

    Hi Shyam,
    Thanks Shyam,
    I check this note this is not applicable for my system, In mention note Correction delivered in Support Package 600.
    but support Package in my system SAP_APPL 603 SAPKH60303,
    Is there any other note or solution for 603 SP
    Thanks
    Dinesh

Maybe you are looking for

  • Firefox won't open mailto links in a new window like it used to...it just opens gmail in the current tab.

    I recently upgraded firefox and now whenever I click a mailto link it opens gmail in the current tab rather than in a new window. How can I get it to open email links in a new window.

  • Wire transfer for Sweden Vendor

    Hello Experts, We have a new foreign vendor from Sweden and we have to pay him through wire transfer. a) Can someone let me know the configurations required to pay this vendor through wire transfer. This is kind of urgent as the payment due date is v

  • Submit Button PDF

    Hi I'm sure there is an answer to this already but here we go. I'm new to creating PDF form. All I want to do is create a form that i send to our contacts they complete it and send it back as a completed form. At the moment I'm getting an XML file ba

  • Algorithim for word-letters jumbler

    Hi! i'm new here and i just want to ask some stuffs about my current simple java project. it's a word game and can somebody give me some tips about how i can create a method for jumbling letters to form all possible words in a given 6-letter word? e.

  • Screen share without authorisation?

    i wandered if i could screen share from my mac mini upstairs without running up there to click the ok screen share pop up window. i'm using the same ichat login on each machine. (other machine macbook pro)