Error when deploying SSIS package in 2012

Hi,
I am trying to deploy a SSIS package to 2012 version. But i am getting error as  below,
TITLE: SQL Server Integration Services
There was an exception while loading Script Task from XML: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.<CleanUp>b__1b()
   at Microsoft.SqlServer.IntegrationServices.VSTA.MtaExecution.Run(Action action)
   at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.CleanUp()
   at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.DisposeVstaHelper()
   at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.MigrateVSTA21ScriptProject(XmlElement elemProj, IDTSInfoEvents events)
   at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
There are 4 packages of same version,  i get this error only for 2 packages and other 2 am able to deploy successfully. Can someone tel mewhat would be the issue.
the same package is successfully deployed from my colleague machine.
Mano

Hi Manon,
According to the error message, the packages that cannot be deployed should include Script Task/Component. But the package that can be deployed without problem include Script Task/Component, right? If so, the issue should occur because certain Visual Studio
Tools for Applications (VSTA) Runtime has been installed:
Microsoft Visual Studio Tools for Application x64 Runtime3.0
Microsoft Visual Studio Tools for Application x86 Runtime3.0
You can check it from the Programs and Features panel. Then, you can install the exact VSTA Runtime from the
\redist\VSTA\runtime\ folder of the SQL Server install media.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
Regards,
Mike Yin
TechNet Community Support

Similar Messages

  • When Deploying SSIS Packages to SQL Server using SSMS Import feature, is the package configuration file deployed at the same time?

    Hello, everyone,
    I have an SSIS package with a XML package configuration file. I deployed it to the sql server using the import feature in SSMS (in Stored Packages, right click MSDB, select Import, select the package to deploy in file system). My question is 
    Is the XML package configuration file also deployed? If so, which folder is it stored so that I can change the values in it? If not, is setting up the Configuration tab when scheduling a agent job the way to go manually bring the configuration file in?
    Your help and information is much appreciated.
    Regards

    Thank you Arthur for your reply. I appreciate it.
    A followup questions:
    I used direct setting for the configuration file path on C:\. But it needs to be on D:\ on the remote server. I can't create the D:\ path because I don't have D:\ drive on my computer (I understand I could use indirect setting to change the path in the remote
    server. But that's not the concern here).
    My question is:  since the configuration is not deployed, can I make it up by setting up the Configurations in creating the agent job step? That is, copy the configuration file to the D:\ drive on the remote server, in Configurations tab, add the configuration
    file on D:\ to the configuration. Will it work? Will the package still look for the original config file on C:\?  and if it doesn't find it there, will it cause any error?
    Thank you in advance for your help.
    Regards

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

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

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

  • I get one or the other error when i install SQL server 2012 SP1 in my Lab server

    I get multiple errors when i install SQL server 2012 SP1 In my lab server.
    Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
    Below are error codes, screen shots and also a log of the error.
    1.  Eror code 0X84B40000
    Also dint understand any thing from this article related to the above error 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
    2. Eror code 0x851A001A
    Can any one plz help as i always get one or the other error.
    ====================================
    Screen shot: 
    Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
    2. Log file content.
    =================================
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2014-05-04 21:15:35
      End time:                      2014-05-04 21:51:45
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  SERVER1
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Enterprise
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 ms\sql
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SCOM
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SCOM
      INSTANCENAME:                  SCOM
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SCOM
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 ms\sql
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           MS\Gautam, MS\SCOM Users
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
    Detailed results:
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

    Sorry about the error in the path, but you find the files that's the main thing.
    Indeed it is a certificate problem:
    2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
    2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
    2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
    Anyway, this blog post,
    http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
    suggests the issue is a corrupted user profile, and you should try to use a different service account.
    This blog also seems to have a simple solution, but I cannot vouch for that it will work:
    http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Getting Error while Execute SSIS Package from Console Application

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

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

  • I have deployed SSIS Package to Integration Services Server, Can i still call them in Parent Package

    i have deployed  SSIS Package to Integration Services Server, Can i  still call them in Parent Package

    Hello,
    In SSIS 2008 you have to adjust your parent package in Visual Studio and point to the deployed package, as ArthurZ stated.
    In SSIS 2012 with projects in project deployment mode this has become easier: you can call the child package in your project from the main package and it will use the package in the development. then you can deploy the project ot SSISDB and the
    Main package in there will call the child packages in the SSISDB.
    Jan D'Hondt - SQL server BI development

  • Error when deploying a map

    hello i have the following error when deploying a map in a local database, the mapping is a simple transfert of data between two table,
    ORA-06550: line 0, column 0:
    ORA-04052: erreurs lors de la consultation de l'objet distant [email protected]@KCDBDEV
    ORA-00604: une erreur s'est produite au niveau SQL récursif 1
    ORA-01882: région de fuseau horaire introuvable
    ORA-02063: pré
    any help please
    thanks,
    tarek

    Hello thank u for helping, i have exactly the same problème in Error executing a query using a DB-Link
    but i am not inderstanding the solution, i found the same probleme in metalink, and the solution posted is:
    1. Create an errorstack of the ORA-1882 to see the ALTER SESSION SET TIME_ZONE statement that is causing the ORA-1882 during deployment. To create this errorstack, follow step 1 to 4 below:
    1. Just before you reproduce the error, open a SQL*Plus session with user SYSTEM.
    SQL> alter system set events '1882 trace name ERRORSTACK level 3'
    2. Deploy the mapping to reproduce the ORA-1882
    3. Disable the system event
    SQL> alter system set events '1882 trace name errorstack off';
    4. Take a look at the errorstack (located in the udump directory). Suppose the following statement is in there:
    ALTER SESSION SET TIME_ZONE = 'GMT+02:00'
    2. Modify the run_service.sh(.bat) file as follow:
    * For UNIX:
    Modify owb_server_home/owb/bin/unix/run_service.sh as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started (last line of run_service.sh)
    $JAVAPATH/bin/java -Xmx768M -Djava.awt.headless=true -DORACLE_HOME.....
    e.g:
    $JAVAPATH/bin/java -Xmx768M -Duser.timezone="+02:00" -Djava.awt.headless=true -DORACLE_HOME
    * For Windows:`
    Modify owb_server_home\owb\bin\win32\run_service.bat as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started
    %JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS%
    e.g.:
    %JAVAPATH%\jre\bin\javaw.exe -Duser.timezone="+02:00" %JVM_OPTIONS%
    3. Save the file and re-start the Runtime Service using stop_service.sql/start_service.sql.
    but in creating the errorstack of the ORA-1882 i not found the ALTER SESSION SET TIME_ZONE
    and i Modify the run_service i fixed -Duser.timezone="+01:00" cause the time zone here is Europe/Paris but there is no changes.
    the db link is from Oracle 10.2.0.2.0 to 9.2.0.1.0. and owb 10g R2
    other solution?
    thanks,
    tarek

  • Error when deploying ear file

    Hello
    What could be the problem that I get this error when deploying my ear file with a web service within.
    [#|2008-03-29T17:43:02.640+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=12;_ThreadName=Thread-26;_RequestID=0a164c90-57bc-4d4a-8b3f-270fc4584891;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-apps\agency_app\agency_jar\META-INF\wsdl\AgencyModuleWebServiceService.wsdl (The system cannot find the file specified)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
         at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
         at java.net.URL.openStream(URL.java:1007)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:699)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:643)
         at com.sun.enterprise.deployment.backend.WebServiceDeployer.doWebServiceDeployment(WebServiceDeployer.java:165)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:855)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:339)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:222)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:359)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:214)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    |#]when I deployed this application on a custom domain setup, it does not fail. But it fails on default domain.
    Regards
    Michael

    How did you create your datasource, can you post the content, without passwords of course.
    Greetings.

  • Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager

    Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
    when I check on Microsoft site it says
    Reports are not upgraded when you upload a report definition file directly to the report server
    or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
    created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
    This is the only way you can upgrade a report definition file.
    Now here is another confusing statement which says
    You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
    2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
    unchanged.
    All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
    2012?
    <o:p>
    </o:p>
    Mudassar

    I have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
    No Migration is required .
    I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
    "You
    can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
    Microsoft needs to correct this the documentation is misleading
    Mudassar

  • Getting Error when deploying the WD application

    hi all,
    Anybody have idea about , what is the reason for the following error. Till now it is working properly. suddenly it is giving the following error when deploying the application.
    2.4.2007 13:17:36 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [004]Deployment aborted
    Settings
    SDM host : eimkopdvs4
    SDM port : 50118
    URL to deploy : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
    Result
    => deployment aborted : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
    Aborted: development component 'TestWebDynproProj'/'local'/'LOKAL'/'0.2007.04.02.13.17.28'/'0':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [EIMKOPDVS4] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
         at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:167)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
         at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
         at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
         ... 37 more
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.4.71.36,port=50104,localport=3057]
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
         ... 1 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi,
    Check if the server is running. If so, try restarting it and then retry.

  • Invalid change to class error when deploying EJB

    We have EJBs that were built by Webgain Visual Cafe and successfully deploy
    to WLS 5.1. We then use the WLE EJB Deployer Tool to build WLE container
    classes and deploy the same EJBs in WLE 5.1.
    One EJB does not deploy in WLE. The ULOG error message is:
    133929.EA-LAWSTUC!JavaServer.517: main: IJENGINE_CAT:150: ERROR: Invalid
    change to class service.Request
    133929.EA-LAWSTUC!JavaServer.517: main: EJB_CAT:29: ERROR: While deploying
    jar ServiceEJB : com.beasys.weblogic.classloader.RedeploymentException:
    ERROR: Invalid change to class service.Request
    133929.EA-LAWSTUC!JavaServer.517: Finalizer: IJENGINE_CAT:152: INFO: Closing
    jar C:\aj\ServiceEJB_WLE.jar
    Does anyone know what can cause an "invalid change to class" error when
    deploying to WLE 5.1? Especially since the EJB deploys successfully in
    WLS.
    Carl Lawstuen

    Reason: database keeps a reference of the class in JAVA$CLASS$MD5$TABLE table. This table keeps a refrence to all java classes loaded in database, and is present in each schema you deploy classes. That's the reason why if you change the application module name, you can load this classes. It instead keeps a reference if you use DROP JAVA CLASS command to drop a java class from de database. Use DROP JAVA command to clear the reference of the dropped classes when dropping it.
    You can see this table as a class dictionary of the database, and you don't have to handle this records manually.

  • How to deploy SSIS packages and jobs that run the package?

    I am fairly new to deploying SSIS packages. We are migrating servers and I need to deploy the packages to the new dev and prod servers. Can you please walk me through this? Also is there a configuration through which we can specify connection strings so
    that it is not dependent on a particular environment?
    Anonymous

    Hi Devcoder,
    As Visakh16 suggested above, we can use deployment utility to deploy SSIS packages to production server. Here are some good articles regarding this topi for your reference, please see:
    Deploying SSIS Packages on to Production Server:
    http://sqlbiblog.blogspot.com/2011/02/deploying-ssis-packages-on-to.html
    Package Deployment (SSIS):
    http://msdn.microsoft.com/en-us/library/ms137592.aspx
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

  • Using ADWrapper but has error when deploy to IIS

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??
    Hi,
    I am moving this thread to Using Forums >Where is the Forum For…?
    forum, the owner of the forum will direct you to a proper forum.
    I would recommend you check this thread
    http://social.msdn.microsoft.com/Forums/en-US/13bb6961-720d-4604-8eff-22251604cd94/active-directory?forum=whatforum
     which shared a place where you could get help, and since this thread has lasted for a long time, you could create a new thread of that forum to get supports.
    Hello,
    Thank you for the post.  I would suggest posting your question in one of the below mentioned Web sites. Hope this helps you.
    http://social.technet.microsoft.com/Forums/en/winserverDS/threads
    http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.active_directory&cat=en_us_5bd43452-4bab-4720-8df9-d5f37d3153b9&lang=en&cr=us
    Have a great day!
    Tier 2 Application Support  Server and Tools Online Operations Team
    Thanks for your understanding.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Gettind error when deploying XI module

    Hi,
    I am getting the following error when deploying XI module in J2EE Engine. can anyone help me to proceed. Thanks.
    08/02/22 16:16:59 -  Start updating EAR file...
    08/02/22 16:16:59 -  start-up mode is lazy
    08/02/22 16:17:12 -  EAR file updated successfully for 13047ms.
    08/02/22 16:17:12 -  Start deploying ...
    08/02/22 16:18:27 -  EAR file uploaded to server for 2656ms.
    08/02/22 16:18:29 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/SignEncrypt..
                         Reason: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey;
                              at java.lang.Class.getDeclaredFields0(Native Method)
                              at java.lang.Class.privateGetDeclaredFields(Class.java:1522)
                              at java.lang.Class.getDeclaredFields(Class.java:1098)
                              at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:78)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)

    Hi Indira.
    As I can see in your log, you're getting the exception
    Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey
    May be you need to include aii_af_svc.jar (AuditLog classes are located into this JAR library) in your EAR archive.
    Regards,
    Gari.

  • Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

    Hello,
    I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
    0 The package executed successfully.
    1 The package failed.
    3 The package was canceled by the user.
    4 The utility was unable to locate the requested package. The package could not be found.
    5 The utility was unable to load the requested package. The package could not be loaded.
    6 The utility encountered an internal error of syntactic or semantic errors in the command line.
    Details:
    I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
    it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
    Here I receives error code 1.
    Can anyone help me to resolve this issue please?
    Thanks in advance!
    CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
     @strPackage nvarchar(100)
    AS
    BEGIN
     -- SET NOCOUNT ON added to prevent extra result sets from
     -- interfering with SELECT statements.
     SET NOCOUNT ON;
     DECLARE @cmd VARCHAR(8000)
     DECLARE @Result int
     DECLARE @Environment VARCHAR(100)
        SELECT @Environment = Waarde
     FROM  Sys_Settings
     WHERE Optie = 'Omgeving'
     --print @Environment
     SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
     SET @cmd = 'dtexec /SQL ' + @strPackage +  ' /SERVER "w2250\NGSQLSERVER"  /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
     --print @cmd
     EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
     --print @Result
    END

    It has something to do with the security.
    E.g. cmdshell is not enabled or the caller has not rights over the package.
    There could be a syntax error, too.
    I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
    sp_start_job <job name>
    Arthur
    MyBlog
    Twitter

Maybe you are looking for