Error while renewing the certificate in SSLM

Hi,
While renewing the certificate on SSLM I am getting the following error
% failed to parse or verify imported certificate.
I am able to upload root certificate successfully.
I am sure that I renewed the certificate using the correct parameters.
Please advise
Regards
Jithesh

Hi Jithesh,
This error can occur when you install the identity certificate and do not have the correct intermediate or root CA certificate authenticated with the associated trustpoint. You must remove and reauthenticate with the correct intermediate or root CA certificate. Contact your 3rd party vendor in order to verify that you received the correct CA certificate.
Cheers!!
Sachin

Similar Messages

  • Wrong Pin error while renewing SAprouter certificate

    Hi,
    i tried renewing Saprouter certificate from marketplace.
    while installing the certificate using the command below, we get the following error.
    E:\usr\sap\saprouter>sapgenpse import_own_cert -c srcert.txt -p local.pse
    import_own_cert: Couldn't open PSE "E:\usr\sap\saprouter\local.pse"
    ERROR in af_open: (1824/0x0720) Wrong PIN for PSE
    ERROR in secsw_open: (1824/0x0720) Wrong PIN for PSE
    ERROR in sec_parse_PSEInfo_cont: (1824/0x0720) Wrong PIN for PSE
    Please suggest a solution for this issue. Is there any command to install the certificate by providing the PIN which we have given while generating local.PSE file.
    Thank you.

    Hi Mamta,
    Did you goted the solution as mark issue.
    If yes kindly share the solution, i am getting same issue.
    Waiting for ur reply.
    Thanks
    Santosh

  • Error while accesing the certificate request service

    Hi,
    I am trying to use certification request available in sicf
        default_host| bc | bsp | sap | certreq .
    I am getting the following error
    Error: Incorrect certificate request (CertReq)
    One of the following reason can cause this error:
    - You call this service without CertReq
    - Your CertReq is not valid or the signature is incorrect
    - Your RA is not registered yet
    - You apply for certificate within incorrect naming space
    Please contact your system administrator.
    Any idea how can i rectify the problem.  Do i need to have any certficate installed in my browser before calling this?
    Regards,
    Dhana

    Hello,
    This is not security related,please ask basis consultant to fix this
    Thanks,
    Prasant

  • Sequence tag error while importing the SSL certificate into ".keystore" fil

    I have created the ".keystore " file successfully and also imported the "root.cer".
    but while importing the SSL certificate it says like
    "keytool error: java.security.cert.CertificateException: IOException: Sequence ta
    g error" (I got the certificate from Verisign)
    How to resolve this Error?
    can anyone help me?
    mail to:: [email protected]
    Thanks in Advance

    Hi,
    I resolved this error by making it sure that there are no extra spaces or unwanted caracter copied while copying the certificate response from the CA. Make sure you are copying the certificate response properly. In my case, some extra space was getting copied so after re-copyinf it properly, it worked.

  • SSPR registration and reset started to fail after renewing the certificates

    Hi,
    On our FIM 2010 R2 environment (version 4.1.3599.0), after renewing the certificates used on FIM Service/Portal and Password Reset/Registration servers two days back, both the password registration and reset no longer work but instead fails on the  last
    step of the process. So for example when user browse to https://passwordreset.domain.com and fills in their domain\username and click next, FIM will send a security code (SMS OTP) to user´s mobile phone and once user then fills in code and click Next, the
    Communication error 3008 is shown to user. Same happens in the last step of the registration where user reviews that the mobile number is correct before clicking finally next. Once clicked the same error as is with Reset portal is shown to user. 
    Other changes than renewing the certificates have not been done to the environment after it was working last time two days ago. Synchronization of users/groups create in FIM Portal works normally towards AD.
    All servers within FIM environment are on same domain and subnet and firewall is off on all servers.
    The following error message as an example is recorded on FIM app log on either of the SSPR servers (two in NLB):
    The error page was displayed to the user.
    Details:
    Title: Communication Error
    Message: An error has occurred. Please try again, and if the problem persists, contact your help desk or system administrator. (Error 3008)
    Source: 
    Attributes: 
    Details: Microsoft.IdentityManagement.CredentialManagement.Portal.Exceptions.GenericCommunicationException: An error occurred while receiving the HTTP response to http://fimservice.domain.com:5726/ResourceManagementService/SecurityTokenService/Registration.
    This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.ServiceModel.CommunicationException:
    An error occurred while receiving the HTTP response to http://fimservice.domain.com:5726/ResourceManagementService/SecurityTokenService/Registration. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an
    HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException:
    Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    The following error message as an example is recorded on FIM app log on either of the FIM Service/Portal servers (two in NLB):
    Microsoft.ResourceManagement.Service: System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.ResourceManagement.WebServices.SecurityTokenService.TokenIssuer.IssueSecurityToken(Message requestMessage, Object request, Claim[] claims)
       at Microsoft.ResourceManagement.WebServices.SecurityTokenService.Challenger.IssueAuthenticationChallenge(Message requestMessage, Object requestBody, Nullable`1 requestContext, UniqueIdentifier authenticationProcessIdentifier, List`1 accumulatedClaims,
    Nullable`1& currentWorkflowInstanceIdentifier, AuthenticationChallengeType[]& currentChallenges)
       at Microsoft.ResourceManagement.WebServices.SecurityTokenService.ProcessRequest(Message requestMessage, Object requestBody)
       at Microsoft.ResourceManagement.WebServices.SecurityTokenService.RequestSecurityTokenResponse(Message requestMessage)
    Both http://fimservice.domain.com:5726 or http://fimservice.domain.com:5725 can be accessed ok using web browser from the SSPR servers. The url of http://fimservice.domain.com:5726/ResourceManagementService/SecurityTokenService/Registration gives http 400 bad
    request which is ok.
    At least the following fixes provided on urls below have been tried out or were in place already but did not fix the issue:
    http://social.technet.microsoft.com/wiki/contents/articles/24629.fim-troubleshooting-sspr-registration-error-3008-an-error-occurred-while-receiving-the-http-response.aspx
    https://social.technet.microsoft.com/Forums/en-US/ae16496e-413a-45b7-a0d1-b39652c6478a/fim-password-registration-portal-error-3008-communication-error?forum=ilm2 (we have exactly the same three errors on FIM app log as mentioned in this post)
    https://social.technet.microsoft.com/Forums/en-US/aa14cff7-6b93-4413-8c75-737dd08bd25f/error-when-resetting-password-on-sspr?forum=ilm2
    https://social.technet.microsoft.com/Forums/en-US/aab6d5ef-667a-4ea9-876d-415c56852da9/sspr-password-reset-failure?forum=ilm2 (no such lines on FIMService config files)
    Can anyone help us with this and provide some tips what to check next on the environment? As the most weird thing here is that everything was working just fine before the certificates were renewed on all servers and no other changes were done on the environment. 
    -Pappa75

    Hi,
    Have you Stop-Start the FIM Service? If not then try this after performing this step. Also, there may be a possibility that the service won't be able to start if there is issue with the certificate.
    The SSPR issue is related to certificate only, which might have some missmatch in the thumbprint value or some other problem.
    If there is a problem with thumbprint of certificate, then you might see error in the Event Viewer and which can be resolved by making the certificate's thumbprint same within registry.
    Regards,
    Manuj Khurana

  • 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 installing the named instance SQL 2012 Sp1

    Hi,
    I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
    during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
    Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
    Shailendra Dev

    thanks alberto.
    here is 
    2015-03-24 19:48:49.42 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
    Oct 19 2012 13:38:57 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
    2015-03-24 19:48:49.42 Server      (c) Microsoft Corporation.
    2015-03-24 19:48:49.42 Server      All rights reserved.
    2015-03-24 19:48:49.42 Server      Server process ID is 3460.
    2015-03-24 19:48:49.42 Server      System Manufacturer: 'Xen', System Model: 'HVM domU'.
    2015-03-24 19:48:49.42 Server      Authentication mode is WINDOWS-ONLY.
    2015-03-24 19:48:49.42 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
    2015-03-24 19:48:49.42 Server      The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
    2015-03-24 19:48:49.42 Server      Registry startup parameters: 
    -d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
    -e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
    -l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
    2015-03-24 19:48:49.42 Server      Command Line Startup Parameters:
    -s "SCSMDB"
    -m "SqlSetup"
    -T 4022
    -T 4010
    -T 1905
    -T 3701
    -T 8015
    2015-03-24 19:48:49.69 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2015-03-24 19:48:49.69 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-03-24 19:48:49.69 Server      Detected 15624 MB of RAM. This is an informational message; no user action is required.
    2015-03-24 19:48:49.69 Server      Using conventional memory in the memory manager.
    2015-03-24 19:48:49.98 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2015-03-24 19:48:50.01 Server      This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
    2015-03-24 19:48:50.03 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2015-03-24 19:48:50.07 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2015-03-24 19:48:50.30 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2015-03-24 19:48:50.58 spid5s      Warning ******************
    2015-03-24 19:48:50.65 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2015-03-24 19:48:50.66 spid5s      Starting up database 'master'.
    2015-03-24 19:48:50.90 spid5s      9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.04 Server      CLR version v4.0.30319 loaded.
    2015-03-24 19:48:51.17 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.17 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.39 Server      Software Usage Metrics is enabled.
    2015-03-24 19:48:51.81 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:51.83 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2015-03-24 19:48:51.86 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:52.02 spid5s      SQL Trace ID 1 was started by login "sa".
    2015-03-24 19:48:52.16 spid5s      Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
    2015-03-24 19:48:52.35 spid12s     The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
    2015-03-24 19:48:52.35 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
    2015-03-24 19:48:52.40 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
    This is an informational message only. No user action is required.
    2015-03-24 19:48:52.43 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
    authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
    2015-03-24 19:48:52.45 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
    message. No user action is required.
    2015-03-24 19:48:54.03 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    2015-03-24 19:48:54.03 spid14s     A new instance of the full-text filter daemon host process has been successfully started.
    2015-03-24 19:48:54.86 spid6s      Starting up database 'mssqlsystemresource'.
    2015-03-24 19:48:54.86 spid5s      Starting up database 'msdb'.
    2015-03-24 19:48:54.87 spid6s      The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
    2015-03-24 19:48:55.21 spid5s      12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid5s      0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid6s      Starting up database 'model'.
    2015-03-24 19:48:55.32 spid5s      Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.72 spid6s      Clearing tempdb database.
    2015-03-24 19:48:57.22 spid6s      Starting up database 'tempdb'.
    2015-03-24 19:48:59.04 spid5s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:48:59.04 spid5s      Starting execution of PRE_MSDB.SQL
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:49:00.23 spid5s      Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.57 spid5s      Starting execution of PRE_SQLAGENT100.SQL
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.61 spid5s      Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.78 spid5s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2015-03-24 19:49:01.79 spid5s      Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    2015-03-24 19:49:01.81 spid5s       
    2015-03-24 19:49:01.81 spid5s      Creating table temp_sysjobschedules
    2015-03-24 19:49:01.91 spid5s       
    2015-03-24 19:49:01.91 spid5s      Alter table sysdownloadlist...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobhistory...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table systargetservers...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobsteps...
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s       
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:01.99 spid5s      Execution of PRE_SQLAGENT100.SQL complete
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:02.01 spid5s      DMF pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      DC pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      Check if Data collector config table exists...
    2015-03-24 19:49:02.13 spid5s      Data Collector state before upgrade: 0
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Check if syscollector_collection_sets_internal table exists...
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Capturing Collection set status in temp table...
    2015-03-24 19:49:02.19 spid5s      Deleting cached auto-generated T-SQL Data Collection packages from msdb...
    2015-03-24 19:49:02.19 spid5s      End of DC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      DAC pre-upgrade steps...
    2015-03-24 19:49:02.19 spid5s      Starting DAC pre-upgrade steps ...
    2015-03-24 19:49:02.19 spid5s      End of DAC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.19 spid5s      Starting execution of MSDB.SQL
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.27 spid5s      Checking the size of MSDB...
    2015-03-24 19:49:02.53 spid5s       
    2015-03-24 19:49:02.53 spid5s      Setting database option TRUSTWORTHY to ON for database 'msdb'.
    2015-03-24 19:49:02.53 spid5s      Setting database option RECOVERY to SIMPLE for database 'msdb'.
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB.SQL
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Starting execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Dropping view MSdatatype_mappings...
    2015-03-24 19:49:02.65 spid5s      Dropping view sysdatatypemappings...
    2015-03-24 19:49:02.65 spid5s      Dropping table MSdbms_datatype_mapping...
    2015-03-24 19:49:02.66 spid5s      Dropping table MSdbms_map...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms_datatype...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms...
    2015-03-24 19:49:02.73 spid5s      Creating table MSdbms
    2015-03-24 19:49:02.75 spid5s      Creating table MSdbms_datatype
    2015-03-24 19:49:03.01 spid5s      Creating table MSdbms_map
    2015-03-24 19:49:03.02 spid5s      Creating table MSdbms_datatype_mapping
    2015-03-24 19:49:03.03 spid5s      Definining default datatype mappings
    2015-03-24 19:49:03.04 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE8
    2015-03-24 19:49:03.21 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE9
    2015-03-24 19:49:03.29 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE10
    2015-03-24 19:49:03.37 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE11
    2015-03-24 19:49:03.46 spid5s      Creating datatype mappings for MSSQLSERVER to DB2
    2015-03-24 19:49:03.54 spid5s      Creating datatype mappings for MSSQLSERVER to SYBASE
    2015-03-24 19:49:03.62 spid5s      Creating datatype mappings for ORACLE8 to MSSQLSERVER
    2015-03-24 19:49:03.71 spid5s      Creating datatype mappings for ORACLE9 to MSSQLSERVER
    2015-03-24 19:49:03.83 spid5s      Creating datatype mappings for ORACLE10 to MSSQLServer
    2015-03-24 19:49:03.95 spid5s      Creating datatype mappings for ORACLE11 to MSSQLServer
    2015-03-24 19:49:04.08 spid5s      Creating view MSdatatype_mappings
    2015-03-24 19:49:04.08 spid5s      Creating view sysdatatypemappings
    2015-03-24 19:49:05.08 spid5s       
    2015-03-24 19:49:05.08 spid5s      Creating table syssubsystems...
    2015-03-24 19:49:05.09 spid5s       
    2015-03-24 19:49:05.09 spid5s      Creating view sysproxyloginsubsystem_view...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating trigger trig_sysoriginatingservers_delete...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating view sysoriginatingservers_view...
    2015-03-24 19:49:05.12 spid5s       
    2015-03-24 19:49:05.12 spid5s      Creating trigger trig_sysjobs_insert_update...
    2015-03-24 19:49:05.13 spid5s       
    2015-03-24 19:49:05.13 spid5s      Creating view sysjobs_view...
    2015-03-24 19:49:05.15 spid5s       
    2015-03-24 19:49:05.15 spid5s      Creating trigger trig_sysschedules_insert_update...
    2015-03-24 19:49:05.16 spid5s       
    2015-03-24 19:49:05.16 spid5s      Creating view sysschedules_localserver_view...
    2015-03-24 19:49:05.21 spid5s       
    2015-03-24 19:49:05.21 spid5s      Creating view systargetservers_view...
    2015-03-24 19:49:05.23 spid5s       
    2015-03-24 19:49:05.23 spid5s      Creating view sysalerts_performance_counters_view...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SNAME ...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SID ...
    2015-03-24 19:49:05.26 spid5s       
    2015-03-24 19:49:05.26 spid5s      Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_category_identifiers...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating function agent_datetime...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_proxy_identifiers...
    2015-03-24 19:49:05.28 spid5s       
    2015-03-24 19:49:05.28 spid5s      Creating procedure sp_verify_credential_identifiers...
    2015-03-24 19:49:05.29 spid5s       
    2015-03-24 19:49:05.29 spid5s      Creating procedure sp_verify_subsystems...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_subsystem_identifiers...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_login_identifiers...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_verify_proxy...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_add_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_delete_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_update_proxy...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_sqlagent_is_member...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_verify_proxy_permissions...
    2015-03-24 19:49:05.34 spid5s       
    2015-03-24 19:49:05.34 spid5s      Creating procedure sp_help_proxy...
    2015-03-24 19:49:05.35 spid5s       
    2015-03-24 19:49:05.35 spid5s      Creating procedure sp_get_proxy_properties...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_proxy_to_subsystem...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_login_to_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_login_from_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_proxy_from_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_proxy_for_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_login_for_proxy...
    2015-03-24 19:49:05.39 spid5s       
    2015-03-24 19:49:05.39 spid5s      Creating procedure sp_reassign_proxy...
    2015-03-24 19:49:05.40 spid5s       
    2015-03-24 19:49:05.40 spid5s      Creating procedure sp_sqlagent_get_startup_info...
    2015-03-24 19:49:05.41 spid5s       
    2015-03-24 19:49:05.41 spid5s      Creating procedure sp_sqlagent_update_agent_xps...
    2015-03-24 19:49:05.42 spid5s       
    2015-03-24 19:49:05.42 spid5s      Creating procedure sp_sqlagent_has_server_access...
    2015-03-24 19:49:05.45 spid5s       
    2015-03-24 19:49:05.45 spid5s      Creating procedure sp_sqlagent_get_perf_counters...
    2015-03-24 19:49:05.46 spid5s       
    2015-03-24 19:49:05.46 spid5s      Creating procedure sp_sqlagent_notify...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_is_sqlagent_starting...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_verify_job_identifiers...
    2015-03-24 19:49:05.48 spid5s       
    2015-03-24 19:49:05.48 spid5s      Creating procedure sp_verify_schedule_identifiers...
    2015-03-24 19:49:05.49 spid5s       
    2015-03-24 19:49:05.49 spid5s      Creating procedure sp_verify_jobproc_caller...
    2015-03-24 19:49:05.50 spid5s       
    2015-03-24 19:49:05.50 spid5s      Creating procedure sp_downloaded_row_limiter...
    2015-03-24 19:49:05.51 spid5s       
    2015-03-24 19:49:05.51 spid5s      Creating procedure sp_post_msx_operation...
    2015-03-24 19:49:05.54 spid5s       
    2015-03-24 19:49:05.54 spid5s      Creating procedure sp_verify_performance_condition...
    2015-03-24 19:49:05.58 spid5s       
    2015-03-24 19:49:05.58 spid5s      Creating procedure sp_verify_job_date...
    2015-03-24 19:49:05.59 spid5s       
    2015-03-24 19:49:05.59 spid5s      Creating procedure sp_verify_job_time...
    2015-03-24 19:49:05.61 spid5s       
    2015-03-24 19:49:05.61 spid5s      Creating procedure sp_verify_alert...
    2015-03-24 19:49:05.62 spid5s       
    2015-03-24 19:49:05.62 spid5s      Creating procedure sp_update_alert...
    2015-03-24 19:49:05.63 spid5s       
    2015-03-24 19:49:05.63 spid5s      Creating procedure sp_delete_job_references...
    2015-03-24 19:49:05.65 spid5s       
    2015-03-24 19:49:05.65 spid5s      Creating procedure sp_delete_all_msx_jobs...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_target_server_job_assignment_sql...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_server_description...
    2015-03-24 19:49:05.67 spid5s       
    2015-03-24 19:49:05.67 spid5s      Creating procedure sp_msx_set_account...
    2015-03-24 19:49:05.68 spid5s       
    2015-03-24 19:49:05.68 spid5s      Creating procedure sp_msx_get_account...
    2015-03-24 19:49:05.69 spid5s       
    2015-03-24 19:49:05.69 spid5s      Creating procedure sp_delete_operator...
    2015-03-24 19:49:05.70 spid5s       
    2015-03-24 19:49:05.70 spid5s      Creating procedure sp_msx_defect...
    2015-03-24 19:49:05.71 spid5s       
    2015-03-24 19:49:05.71 spid5s      Creating procedure sp_msx_enlist...
    2015-03-24 19:49:05.72 spid5s       
    2015-03-24 19:49:05.72 spid5s      Creating procedure sp_delete_targetserver...
    2015-03-24 19:49:05.73 spid5s       
    2015-03-24 19:49:05.73 spid5s      Creating procedure sp_enlist_tsx
    2015-03-24 19:49:05.74 spid5s       
    2015-03-24 19:49:05.74 spid5s      Creating procedure sp_get_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Create procedure sp_set_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Creating procedure sp_add_targetservergroup...
    2015-03-24 19:49:05.77 spid5s       
    2015-03-24 19:49:05.77 spid5s      Creating procedure sp_update_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_delete_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_help_targetservergroup...
    2015-03-24 19:49:05.79 spid5s       
    2015-03-24 19:49:05.79 spid5s      Creating procedure sp_add_targetsvgrp_member...
    2015-03-24 19:49:05.80 spid5s       
    2015-03-24 19:49:05.80 spid5s      Creating procedure sp_delete_targetsvrgrp_member...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_verify_category...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_add_category...
    2015-03-24 19:49:05.82 spid5s       
    2015-03-24 19:49:05.82 spid5s      Creating procedure sp_update_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.83 spid5s      Creating procedure sp_delete_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_category...
    2015-03-24 19:49:05.84 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_targetserver...
    2015-03-24 19:49:05.85 spid5s       
    2015-03-24 19:49:05.85 spid5s      Creating procedure sp_resync_targetserver...
    2015-03-24 19:49:06.06 spid5s       
    2015-03-24 19:49:06.06 spid5s      Creating procedure sp_purge_jobhistory...
    2015-03-24 19:49:06.09 spid5s       
    2015-03-24 19:49:06.09 spid5s      Creating procedure sp_help_jobhistory...
    2015-03-24 19:49:06.10 spid5s       
    2015-03-24 19:49:06.10 spid5s      Creating procedure sp_add_jobserver...
    2015-03-24 19:49:06.11 spid5s       
    2015-03-24 19:49:06.11 spid5s      Creating procedure sp_delete_jobserver...
    2015-03-24 19:49:06.11 spid5s      Error: 10011, Severity: 16, State: 1.
    2015-03-24 19:49:06.11 spid5s      Access denied.
    2015-03-24 19:49:06.11 spid5s      Error: 917, Severity: 15, State: 1.
    2015-03-24 19:49:06.11 spid5s      An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message  for the line which caused compilation to fail.
    2015-03-24 19:49:06.11 spid5s      Error: 912, Severity: 21, State: 2.
    2015-03-24 19:49:06.11 spid5s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
    operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
    actions and re-start the database so that the script upgrade steps run to completion.
    2015-03-24 19:49:06.11 spid5s      Error: 3417, Severity: 21, State: 3.
    2015-03-24 19:49:06.11 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
    Online.
    2015-03-24 19:49:06.12 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2015-03-24 19:49:06.50 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    Shailendra Dev

  • RWI 00200 Error while scheduling the Bex Query based Webi report

    Dear All,
    I am facing the below error while scheduling the Bex Query based Webi report.
    Error:RWI 00200
    We are using BO XI 4.0 Sp05.
    Please advise

    Hi,
    I am on BO 4.0 SP05 Patch 6. Webi reports are just showing processing but not giving results. When I try to create new report it is throwing java security error.
    Tried applet patch upgrade(From link : https://websmp207.sap-ag.de/~sapidb/011000358700000902752013E) for webi certificate but didn't help.
    Please suggest what could be done.
    Thanks and Regards,
    Ankit Sharma

  • I have error while testing the system created from a sap business objects template in SAP portal

    I have error while testing the system created from a sap business objects template in SAP portal. Error text:
    com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not create JCO connection. 'mshost' missing
    I configure integration SAP portal and SAP BW system. All system requirements are complied.
    Environment
    SAP Business Objects 4.0
    SAP BW 7.31
    1.     I configure SSSO between SAP BW and SAP Business Objects Enterprise 4.0
    2.     Next I setting integration SAP PORTAL with SAP BW system
    3.     I download certificate from portal. Select Certificates and key (http://sapserver:port/nwa) – See scren_
    4.     In next window selected Ticketkeystore and Saplogonticketpair-cert( near part window form)
    5. Select Export entry button and binary format file certificate for download. Press download.
    6.     Save certificate file in local PC folder
    In next step need export certificate file to SAP system. Sequence of step:
    1.       Run STRUSTSS02 transaction .
    2.       Chose certificate ->import.
    3.       Select downloaded certificate file
    4.       Select Add to certificate list button and Add to ACL button
    5.       Inter System ID and Client(000)
    6.       In next I download iview sap business objects template into sap portal: System administration->transport->Import. And select and download sap business Objects iview template in .epa format into sap portal.
    7.       Result – downloaded iview.
    8.       In next step I create system from template. System administration->system landscape.
    9. In next step I input parameters for my system in Connector category, Sap business objects and user management categories: See screen _2
    10.   When I created the system and test the connection error occurred: See screen_3
    This issue is important enough. I would be grateful for opinions and ideas. Thanks in advance.

    Did you find a solution?

  • Error while creating the HTTP client with destination

    Hi ,
    I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
    Error while creating the HTTP client with destination
    The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
    We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

    Check few things..
    1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
    2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
    3) Make sure certificate is installed as expected.
    4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

  • WS-Security: Error while valdiating the digital signature

    Hi
    We are getting an exception (in the J2EE logs) when an external party calls our SOAP webservice with WS-Security. We are using their public certificate to verify their signature (self signed certificate). Their SOAP Security header looks correct - below is the error in the J2EE logs.
    VerifyException. Key: 0200
    [EXCEPTION]
    com.sap.security.core.policy.exceptions.VerifyException: [_policy0200] Error while valdiating the digital signature. The error was java.lang.NullPointerException null.
    at com.sap.security.core.securitypolicy.assertions.IntegrityAssertion.verify(IntegrityAssertion.java:376)
    at com.sap.security.core.policy.expressions.AllExpression.verify(AllExpression.java:149)
    at com.sap.security.core.policy.WSPolicy.verify(WSPolicy.java:43)
    Any help would be greatly appreciated.

    What do you mean by "external party" and "self signed certificate" in this context?
    A 3rd party vendor or customer is giving you their server's "self signed" certificate to use publicly?
    Apart from this being more prone to admin errors than server certificates already are, I hope that they trust you...
    Cheers,
    Julius

  • Error while launcing the rich pod

    Hello,
    We are getting error while launcing the rich pod after SP5 update in 5.2.
    Error: Jar Resource in JNPL file are not signed by same certificate.
    Regards ,
    Pushkar
    Edited by: Pushkar Patil on Feb 3, 2011 2:52 PM

    PI experts,
    Facing two issues on PI Integration Builder, PI 7.1 has been newly installed in client landscape on Windows & MSSQL database. Being fresh installation we have performed configuration wizard setup as part of the PI post installation procedure.
    ABAP connectivity is fine, while connecting to PI portal to Integration builder we have the same issue what Pushkar Patil had, attaching snapshot. Pushkar replied saying clearing temp files by java application solved his problem. Could any advise me temp location, does he mean C:\TEMP/tmp location?
    Another issue, when we navigate to PI portal, for example http://au0411gol1007:50000/nwa    
    or system information, URL does not give the output, it ends with an error. Screenshot attached for reference.
    Also attaching default trace file for this issue, any help would be of very great help.
    DefaultTrace.trc log ID : 005056004AA4014B0000000000001444
    #2.0 #2013 05 28 05:10:55:238#+00#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
    com.sap.ASJ.web.000137#BC-WD-JAV#sap.com/tc~wd~dispwda#005056004AA4014B0000000000001444#5649150000000004#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#0##40B939F1C75311E2A3F5005056004AA4#40b939f1c75311e2a3f5005056004aa4#40b939f1c75311e2a3f5005056004aa4#0#Thread[HTTP Worker [@427187079],5,Dedicated_Application_Thread]#Java##
    Cannot process an HTTP request to servlet [dispatcher] in [webdynpro/dispatcher] web application.#1#com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to retrieve client for current request. Causing exception is  nested.
        at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:493)
        at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.checkAuthentication(ClientUserFactory.java:200)
        at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory$1.checkAuthentication(AbstractClientUserFactory.java:151)
        at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.checkAuthentication(WDClientUser.java:214)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkAuthentication(RequestManager.java:713)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:237)
        at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
        at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
        at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
        at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
        at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
        at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
        at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
        at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
        at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
        at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)
        at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
        at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.webdynpro.services.cal.core.exceptions.WDClientException: Found no client: clientNameReqParam=null, clientNameAppParam=null, useragent=Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0
        at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.findClientContainer(ClientInspector.java:212)
        at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.getClient(ClientInspector.java:104)
        at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:491)
        ... 51 more

  • Getting error while creating the variable of Schema Element type

    Hi everybody,
    For creating a variable of schema element type I am doing the following steps...
    Select 'Variables' after right clicking on bpel process. IN this window, go to 'Create VAriable' then select 'Element' type. Now in Type Choose, I expanded the my imported schema files. And selected a element type, then click ok to create this variable... I am getting the message...
    IN ORDER TO SAVE IMPORTED WSDL/SCHEMA FILES, YOU MUST HAVE A PARTNER LINK LOCATED UNDER THE CURRENT PROJECT DIRECTORY.
    What is mean by that.
    I have imported the schema files in project. AFter that I have imported them into the WSDL also. Now why I am getting error while creating the variable. However I can create variable directly in .BPEL file then everything is fine. And it is working also. But what is mean with the above error? Why I am not able to create variable through GUI?
    Thanks.

    Hi,
    I have this same problem this morning, and I was going crazy, until I found this webpage on the internet:
    [http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process|http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process]
    The idea is that the jdeveloper is not very good working with directories with spaces on the directory name. If you move all your work to a directory without spaces, it will work smoothly. At least, it had worked for me.
    Regards,
    Nacho

  • Error while creating the DWH tables using DAC

    Hi,
    I am getting error while creating the DWH tables using DAC. I have created a ODBC DSN using merant driver with DAC repository DB credentials and the test connection is successful. And while creating the tables i gave the olap dw credentials and the DSN name which i created earlier. But it throws the error as below:
    Please find the below mentioned error message
    =====================================
    STD OUTPUT
    =====================================
    CREATING SIEBEL DATABASE OBJECTS
    F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ******* /c DB_DAC /G "SSE_ROLE" /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b "" /K "" /X "" /W N
    Error while importing Siebel database schema.
    =====================================
    ERROR OUTPUT
    =====================================
    Siebel Enterprise Applications ODBC DDL Import Utility, Version 7.7 [18030] ENU
    Copyright (c) 2001 Siebel Systems, Inc. All rights reserved.
    This software is the property of Siebel Systems, Inc., 2207 Bridgepointe Parkway,
    San Mateo, CA 94404.
    User agrees that any use of this software is governed by: (1) the applicable
    user limitations and other terms and conditions of the license agreement which
    has been entered into with Siebel Systems or its authorized distributors; and
    (2) the proprietary and restricted rights notices included in this software.
    WARNING: THIS COMPUTER PROGRAM IS PROTECTED BY U.S. AND INTERNATIONAL LAW.
    UNAUTHORIZED REPRODUCTION, DISTRIBUTION OR USE OF THIS PROGRAM, OR ANY PORTION
    OF IT, MAY RESULT IN SEVERE CIVIL AND CRIMINAL PENALTIES, AND WILL BE
    PROSECUTED TO THE MAXIMUM EXTENT POSSIBLE UNDER THE LAW.
    If you have received this software in error, please notify Siebel Systems
    immediately at (650) 295-5000.
    F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ***** /c DB_DAC /G SSE_ROLE /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b /K /X /W N
    Connecting to the database...
    28000: [DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied
    Unable to connect to the database...
    any help is appreciated.
    Thanks,
    RM

    The fact that you are getting an "ORA-01017: invalid username/password; logon denied" message indicates that you are at least talking to the database.
    The log shows that username "infdomain" is being used. Can you double check the username and password you have in DAC in a SQL*Plus/SQL Developer session?
    Please mark if useful/helpful,
    Andy.

  • "Error while registering the Java 2 Runtime Environment registry keys"

    "Error while registering the Java 2 Runtime Environment registry keys"
    I am getting the above error when trying to install the 1.3 JRE (installed with the 1.3 plug in which I need). As part of my development I have been installing and uninstalling the JRE multiple times. Then, I got the above error when trying to install it, and now it appears to be installed but I cannot uninstall it. When I try to uninstall it, it just remains, and when I try to install it again I get the above error. I have tried cleaning up all javasoft registry entries, but it doesnt seem to have helped. Can anyone help me either completely uninstall the JRE so I can do a clean install or help me get rid of the error above when I install. Is there some registry entries I should be looking at? Anything else? this is quite urgent as I need to test my applet with the plugin installed and not installed - and I currently cant uninstall it. Any ideas?
    Thanks for your help
    Aaron

    I am getting this same error message when trying to upgrade from 1.3.1_03 to 1.3.1_19.
    I have multiple versions of jre's and jdks on my machine.
    Anyone else seen this problem or know how to resolve it.

Maybe you are looking for