Error "To run a SSIS package outside of SQL Server data tools you must install task name used in package of Integration service or highter.

Hello Team,
I am trying to execute a SSIS package from web page. When i try to do that i am getting following error.
"To run a SSIS package outside of SQL Server data tools you must install <task name used in package> of Integration service or highter."
In my machine Integration Services are installed and its service is also in running state.
Please help me on this.
Thanks,
Ramesh
Thanks, Ramesh Arige

The SSIS package developed using SSIS 2008 Server R2 and Integrations Services 10.0 is exists in my machine. Is this wrong configuration, please help me on this.
I am using the below code copied from CodeProject
Thank you so much for responding.
Ramesh
Thanks, Ramesh Arige
Which way are you using from the provided blog? Using 1) C# Code or 2) C# and Stored Procedure?
Cheers,
Vaibhav Chaudhari
MCP, MCTS, MCSA (SQL Server 2012)

Similar Messages

  • SSIS: To run a SSIS package outside of SQL Server Data Tools you must install SCR - DP1 Connections of Integration Services or higher

    We have SSIS installed on a machine that is not part of a cluster but it is accessible by the cluster.
    Our job we have running on the cluster is failing with the following error:
    Error: 2014-01-31 09:14:37.52     Code: 0xC000F427     Source: SCR - DP1 Connections  
    Description: To run a SSIS package outside of SQL Server Data Tools you must install SCR - DP1 Connections of Integration Services or higher.  End Error
    Any advice or information on how to resolve this would be great.
    Many Thanks.

    Hi NessaBella,
    Integration Services service is not a cluster-aware service, and does not support failover from one cluster node to another. Therefore, in a clustered environment, Integration Services should be installed and started as a stand-alone service on each node
    in the cluster.
    Based on the error message, it seems that SSIS is not installed on the cluster node on which the job was running. Although SSIS is installed on a machine that is not part of the cluster and can be accessed by each cluster node, the SSIS service installed
    on a remote server cannot be used a cluster node. So, please install the shared feature SQL Server Integration Services on each cluster node. Besides, if certain packages need to run in 32-bit mode in certain jobs and the SQL Server installed is 64-bit version,
    you also need to install BIDS/SSDT on the cluster node to get the 32-bit runtime of SSIS.
    References:
    Integration Services (SSIS) in a Cluster
    Loading and Running a Remote Package Programmatically
    Regards,
    Mike Yin
    TechNet Community Support

  • Please help with this issue "To Run a SSIS Package outside of Server Data Tools You must install Drived Column of Integration sercvies of higher" From C# app

     i have searched all over the google and here on MSDN(I have read all the threads related to my problem ) , i am new to SISS and doing my clg project ,
    I have this package which loads data from  dim tables to a fact table , my Package runs without any problem in BIDS (2012)
    I have installed SQl Server integration services on SQL and service is also running in services.msc,
    the problem comes when i execute my package using my C# application i am using MSDN Method to execute a SSIS package programmatically given here.
    "http://msdn.microsoft.com/en-us/library/ms136090.aspx"
    For loading my FactTable i have used a Derived columns  and some lookups , 
    Now if i don't use derived columns and looks ups and just use source and destination component then my package runs fine from my C# application but if i use derived columns or looks ups etc it gives the following error
    "Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/SSIS.Pipeline: To Run a SSIS package outside of SQL Server Data Tools you must Install Derived Column of Integration services of higher"
    I am searching and trying to resolve this issue from previous 2 days but without any luck please help or guide me what is solution to this problem ,,i will be very thankful
    I have also found that integration services that are running on my system have version  10.0
    but the BIDS have version Version 11.0.3402.0
    IS this causing problem ?  if yes then what i have to do  ?

    Hi BlaxButt,
    The package is developed in SSDT installed by SQL Server 2012, so it is a SSIS 2012 package. However, the Integration Services you have installed is SQL Server 2008 R2 version. To run the package outside SSDT, you need SSIS 2012 installed. The reason why
    the package runs fine with only Source and Destination components is that such a simple package can be executed by the DTExec utility installed by SQL Server 2012 Data base Engine or Client Tools (SQL Server Import and Export Wizard). To run a package that
    uses other tasks/components outside SSDT/BIDS, the SSIS runtime is also required except the DTExec utility. To obtain the SSIS 2012 runtime, we have to install SSIS 2012 on the server where the package runs.
    Reference:
    http://stackoverflow.com/questions/19989099/getting-error-running-ssis-package-on-non-ssis-server
    Regards,
    Mike Yin
    TechNet Community Support

  • Error installing SQL Server Data Tools - Business Intelligence for Visual Studio 2013

    Hi
    I am trying to install SQL Server Data Tools - Business Intelligence for Visual Studio 2013 and am getting the following error
    This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
    I am running
    Windows 8.1 x64
    SQL Server 2014 Developer Edition x64
    Visual Studio 2013 Professional
    Any help would be appreciated.
    Thanks
    Biztalk Developer

    Could you please check if Windows Installer service is running and is in automatic startup mode.
    The other thing is, if you’re running an x64-based SQL instance (64-bit), make sure to select “New Instance” on the Installation Type page, and NOT “Add features to an existing instance”. 
    http://stackoverflow.com/questions/24989187/64-bit-microsoft-sql-server-data-tools

  • SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI) and SSIS on SQL Server 2012

    This great blog entry titled
    SQL Server Data Tools - Business Intelligence for Visual Studio 2013 (SSDT BI), link below, highlights the lack of support for SSIS projects using SQL Server 2012, VS 2013 and SSDT BI for VS 2013. I see there is a new version
    on SSDT BI for VS 2013 (12.0.2430.0, File Name: SSDTBI_x86_ENU.exe, Date Published: 10/27/2014) link below.
    Does this version support SSIS projects using SQL Server 2012 using VS 2013 and SSDT BI for VS 2013?
    http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
    http://www.microsoft.com/en-us/download/details.aspx?id=42313

    Hi cjrinpdx,
    According to the picture, it seems that we can use SSIS 2012 support is not included in SSDT-BI for VS 2013. And based on the previous versions, SSIS always different from SSRS, SSAS.
    SSDT-BI for Visual Studio 2012 supports versions of SQL Server as follows:
    SSAS project can target SQL 2012 or lower
    SSRS project can target SQL 2012 or lower
    SSIS project can target only SQL 2012
    The following blog is for your reference:
    http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx
    Since I have no environment to test this at this moment,
    I recommend you that submit the feedback at
    https://connect.microsoft.com/SQLServer/. 
    Thank you for your understanding.
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Package migration from SSIS 2008 R2 to SQL server 2012

    hi guys:
      My company has decided to use Sql server 2012 for the database service, Integration service as well as analysis service
      The first question is which tool I should install to run packages ? in SQL Server 2008 R2, I've installed BIDS which is inside the disk.
      Also do I need to install any visual studio tools? I was under the impression that the BIDS 2008 was using kinda shell visual studio. 
     Thanks
     Hui
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Hi cat_ca,
    To develop package in SQL Server 2012 Integration Services, we use the SQL Server Data Tools (SSDT 2012) which can be installed from the SQL Server 2012 install media. The SSDT 2012 use Visual Studio 2010 shell by default and can be integrated into Visual
    Studio 2010. By installing SQL Server Data Tools - Business Intelligence for Visual Studio 2012, we can also integrate SSDT 2012 into Visual Studio 2012. However, SSDT 2012 cannot be integrated into Visual Studio 2013. As far as I know, the SSDT 2014 released
    in SQL Server 2014 RTM will use the Visual Studio 2013 shell and can be integrated into Visual Studio 2013.
    Regards,
    Mike Yin
    TechNet Community Support

  • SSIS package fails in sql server agent wirh 'Process exit code "-532459699" runs fine when run independantly

    I have a SSIS package that fails when running via sql server agent.  I can successfully run it from BIDS.    I have created a proxy account that is in the local server administrators group and is sysadmin.  SQL Server Agent and SQL
    Server Integration Services  are running under the same account,
    following the the error message:
    Error: 2014-02-07 10:29:12.59
       Code: 0xC0029151
       Source: Execute De-linking Execute Process Task
       Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
    End Error
    This package ran successfully on a different server running windows 2003 and sql server 2008 r2.  The new environment is windows 7 with sql server 2008 r2.

    Hi Gaileg,
    As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
    runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
    If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
    SQL Server Agent rather than the SSIS package itself.
    Regards,
    Mike Yin
    TechNet Community Support

  • Individual SSIS Package deployment in SQL server 2012

    Hi,
    I am developing the SSIS packages in sql server 2012.
    I want to know how we can deploy individual SSIS packages as I will be editing the required packages if need be then I have to deploy that package only instead of entire project deployment.
    Please help me on this.
    Regards,
    Ramu
    Ramu Gade

    Hi Ramu,
    According to your description, you want to deploy a single package instead of entire project in SQL Server 2012.
    In SQL Server 2012, the unit of deployment to the SSIS catalog is a SSIS Project. Each SSIS project contains one or more SSIS packages. We couldn’t directly deploy a single package in Project Deployment Model.
    To work around this issue, we can refer to the following suggestions:
    SSMS-->Integration Service Catalogs-->SSISDB-->Your project-->projects. Right click on the projects, and choose "Import Packages...". Then make use of the Project Conversion Wizard to select the packages that you want to deploy, deploy
    the generated .ispac file to SSIS Catalog.
    The command line tool DTUTIL.EXE which can be used to deploy SSIS packages.
    References:
    SQL Server 2012 - Project Deployment Model - Deploy a single package
    Command line deployment tool for SSIS packages
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    This was originally posted in the SSIS Forum, but a member of the IS team suggested it be moved here.  "Most recently I got this error (Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?"
    I'm having the same issue, and here's our scenario:
    Installed SQL Server 2005 Developer Edition on a machine with WinXP SP2 and enabled remote connections over TCP/IP
    Installed SQL Server 2005 Standard Edition on a machine with Win2003 SP1 (remote connections over TCP/IP enabled by default)
    Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'Detach and Attach' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
    Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'SQL Management Objects' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
    Reinstalled Standard Edition on the Win2003 SP1 machine
    Checked all the settings on both machines several times, restarted services etc., and read every post I could find referencing the error.
    Same error
    Lost my last hair
    Thanks in advance,
    Steve

    Nan,
    Before I get on with this post - thank you for your reply.
    The XPSP2 machine actually had the firewall disabled, and I verified that it could accept connections on the the associated ports with the Shields Up utility.  I tested this on both machines.
    I can connect to the server from the XPSP2 machine, Import / Export, manage, view logs, and do everything EXCEPT get the Copy Database package to run.  SQL Server Agent always fails on the last step with the following error:
    Event Type: Error
    Event Source: SQLISPackage
    Event Category: None
    Event ID: 12550
    Date:  1/10/2006
    Time:  1:34:15 PM
    User:  NT AUTHORITY\SYSTEM
    Computer: 401SERVER
    Description:
      Event Name: OnError
     Message: Failed to connect to server BETHESDA.
    StackTrace:    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
       at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server& server, ServerProperty serverProp)
    InnerException-->An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    StackTrace:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
       at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
     Operator: NT AUTHORITY\SYSTEM
     Source Name: BETHESDA_401SERVER_Transfer Objects Task
     Source ID: {86F355AD-3B74-4D7B-8D2D-C743C790A269}
     Execution ID: {91B7C32C-C439-4EDB-8A0F-9F8BF207BC06}
     Start Time: 1/10/2006 1:34:15 PM
     End Time: 1/10/2006 1:34:15 PM
     Data Code: 0
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Have you (or anyone else) successfully executed a Copy Databse task?
    Steve

  • Attunity SSIS connector support for Sql Server 2014?

    Hello,
    We've been successfully using Attunity SSIS connector 2.0 for a couple of years with SQL SERVER 2012.
    We developed some Visual Studio projects and deployed them on our SSISDB. Then launch them with scheduled jobs. Everything worked fine.
    After we upgraded the server to Sql Server 2014 the connector failed with the following error:
    The connection type "MSORA" specified for connection manager "XXX" is not recognized as a valid connection manager type.
    This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
    We tried uninstall/install but was no good. Also 32/64 bits combinations.
    We tried DTEXEC utility and worked fine on sqlserver 2012 folder ( \110\DTS\Binn) but didn't work on 2014's folder ( \120\DTS\Binn).
    We also tried a fresh 2014 installation but keep getting the same error.
    Does Attunity connector 2.0 support Sql Server 2014? If not, should I wait for a new version? Any workaround?
    For now, we are using the DTEXEC utility on 2012's folder, but since we have to use the /sql option (/ISSERVER is not working) we can't pass parameters to the .dtsx package.
    Any help would be much appreciated.
    Regards,
    Daniel

    I'm with Daniel - Microsoft should be taking the lead in resolving this. We downloaded the previous two versions from Microsoft Download (e.g. link below) with no indication that Microsoft would wash their hands of future support.
    http://www.microsoft.com/en-us/download/details.aspx?id=29283
    Attunity have replied on the thread on their forum - saying it is Microsoft's responsibility:
    http://www.attunity.com/forums/microsoft-ssis-oracle-connector/attunity-ssis-connector-support-sql-server-2963.html
    Trying to run, develop and support on parallel versions of SSIS is not a viable solution IMO.
    I will advise all my clients who use these connectors not to upgrade to SQL Server 2014 until this is resolved.

  • SQL Server Agent Log showing errors [298] SQLServer Error: 10061, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL

    Hi All,
    I have started receiving this error in the logs for the last 10 days and the Schedules Jobs for the database have stopped running. My MS CRM application is working fine.
    Can anyone guide me what could be the problem.
    Date                      17/4/2014 2:04:20 PM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct
    and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
    Date                      17/4/2014 2:11:55 PM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    A network-related or instance-specific error
    has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
    see SQL Server Books Online. [SQLSTATE 08001]
    Date                      7/4/2014 11:00:31 AM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    A network-related or instance-specific error
    has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
    see SQL Server Books Online. [SQLSTATE 08001]

    Check this link
    http://social.msdn.microsoft.com/Forums/en-US/906da9b5-2482-468c-a424-ae099da2d96b/sql-server-agent-service-account-error?forum=sqlsetupandupgrade
    Regards, RSingh

  • SQL Server Management Tools - Could not write value to key \SOFTWARE. Error code: 1406

    Detailed Results:
    Feature: Management Tools-Basic
    Status: Failed
    Component Name: Sql Server Management Studio
    Component Error code: 1406
    Error Description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
    The first time the installer worked installing perfectly, but I needed an named instance of "SQL2008", so I removed the instances. After this re-installing is not working.
    From past 3-4 days I went through most of the links which has provided solutions for error code 1406, and not having success for installing.
    I have tried these options,
    1) Ran the installer using "Run as Administrator"option. I am an Administrator user for the machine.
    2) In Registry Editor, right-click HKEY_CURRENT_USER\Software, and then click Permissions. Click Add, type Everyone, and then click OK. Under Group or user names, click Everyone. Under Permissions, click to select Full Control in the Allow column, and then
    click OK.
    3) Uninstalled the Sql server product, and used Revo Uninstaller / CCleaner to clean the registry and the remaining files and folders.
    4) Multiple versions of SQL installers have been tried (SQL 2008/2012/2014)
    5) Logged in as local/Administrator for the machine, tried the similar steps.
    6) The same installers are still working in one of the virtual machines for multiple times of installation and uninstallation without having any problems.
    Please let me know, if needed further information. Please provide help for installing SQL server management studio.
    Regards,
    Ananth.

    I have the same problem.
    I can not install MSSQLManagementStudio. I suppose
    that is not the fault of permissions
    . I have tried to
    install as an administrator
    on the computer in the domain where the account has domain administrator permissions.The account is added to the local administrators.
    I also have tried to install as local administrator
    account after the removal of the domain.
    With the same result.
    Operating System Windows 8.1 Prof.
    I have tried  2012, 2012with SP1 , 2012x86 , 2014. All with same result:
    Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    Other elements installs without any problem.
    sql_ssms_Cpu64_1.log show that the problem is in that point:
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup,,BinaryType=0,,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SqlToolsPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=Path,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SQLPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
    MSI (s) (1C:C0) [10:32:51:834]: Note: 1: 1406 2:  3: SOFTWARE 4: 5
    MSI (s) (1C:C0) [10:33:19:949]: Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    07/30/2014 10:33:19.949 [540]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    ...... rest of the roolbaack next
    As i the lines:
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
    MSI i opening the root hive of HKLM/Softftware
    and MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
    and trying to Add Default Value.
    What is impossible regardless of the
    level of permissions.
    Please provide help for installing SQL server management studin in any version
    Regards,
    Michael

  • Error in ODBC after long time connection (MS.SQL Server 2000)

    i' using windows XP
    and create MS.SQL Server connection through SYSTEM DSN of ODBC DATA SOURCE ADMINISTRATOR in WinXP Control Panel
    using jdbc.odbc connection to make connection to database.
    it's working, but after many request of data transaction with database.
    my program closed it self.
    an a error file appear in the path of program.
    i don't remember all what the error file contain exactly - it's about ODBC connection ( i already remove the error file long day a go, if i got it again i will post it here)
    is java cannot connect database with ODBC properly?
    thanks.

    this is the error:
    # An unexpected error has been detected by HotSpot Virtual Machine:
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c901010, pid=2528, tid=3508
    # Java VM: Java HotSpot(TM) Client VM (1.4.2_15-b02 mixed mode)
    # Problematic frame:
    # C [ntdll.dll+0x1010]
    --------------- T H R E A D ---------------
    Current thread (0x02e64358): JavaThread "ServerBeritaThread" [_thread_in_native, id=3508]
    siginfo: ExceptionCode=0xc0000005, reading address 0x00000018
    Registers:
    EAX=0x00000004, EBX=0x0355f9b4, ECX=0x7ffaf000, EDX=0x00000004
    ESP=0x0355f950, EBP=0x0355f968, ESI=0x00000000, EDI=0x039414e8
    EIP=0x7c901010, EFLAGS=0x00010297
    Top of Stack: (sp=0x0355f950)
    0x0355f950: 74355a16 00000004 0394150c 7432139f
    0x0355f960: 0394150c 00000000 0355f980 7432a244
    0x0355f970: 0394150c 74350000 02e643f4 02e64358
    0x0355f980: 0355f994 7432a653 02fbde98 02e643f4
    0x0355f990: 143aff08 0355f9ac 03711157 039414e8
    0x0355f9a0: 0355f9b4 02e64358 143aff50 0355f9e4
    0x0355f9b0: 00a881a6 00000000 0355fa00 039414e8
    0x0355f9c0: 00000000 0355f9f4 0355f9c8 00000000
    Instructions: (pc=0x7c901010)
    0x7c901000: 90 90 90 90 90 64 8b 0d 18 00 00 00 8b 54 24 04
    0x7c901010: 83 7a 14 00 75 4f f0 ff 42 04 75 19 8b 41 24 89
    Stack: [0x03520000,0x03560000), sp=0x0355f950, free space=254k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C [ntdll.dll+0x1010]
    C [ODBC32.dll+0xa244]
    C [ODBC32.dll+0xa653]
    C [JdbcOdbc.dll+0x1157]
    j sun.jdbc.odbc.JdbcOdbc.allocConnect(J[B)J+0
    j sun.jdbc.odbc.JdbcOdbc.SQLAllocConnect(J)J+30
    j sun.jdbc.odbc.JdbcOdbcDriver.allocConnection(J)J+6
    j sun.jdbc.odbc.JdbcOdbcConnection.initialize(Ljava/lang/String;Ljava/util/Properties;I)V+37
    j sun.jdbc.odbc.JdbcOdbcDriver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;+129
    j java.sql.DriverManager.getConnection(Ljava/lang/String;Ljava/util/Properties;Ljava/lang/ClassLoader;)Ljava/sql/Connection;+154
    j java.sql.DriverManager.getConnection(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/sql/Connection;+41
    j Prosesor.processInput(Ljava/lang/String;)Ljava/lang/String;+51
    j ServerBeritaThread.run()V+35
    v ~StubRoutines::call_stub
    V [jvm.dll+0x752e6]
    V [jvm.dll+0xaf627]
    V [jvm.dll+0x751f3]
    V [jvm.dll+0x74eef]
    V [jvm.dll+0x74f28]
    V [jvm.dll+0x8ce4f]
    V [jvm.dll+0xd3b07]
    V [jvm.dll+0xd3ad5]
    C [MSVCRT.dll+0x2a3b0]
    C [kernel32.dll+0xb50b]
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j sun.jdbc.odbc.JdbcOdbc.allocConnect(J[B)J+0
    j sun.jdbc.odbc.JdbcOdbc.SQLAllocConnect(J)J+30
    j sun.jdbc.odbc.JdbcOdbcDriver.allocConnection(J)J+6
    j sun.jdbc.odbc.JdbcOdbcConnection.initialize(Ljava/lang/String;Ljava/util/Properties;I)V+37
    j sun.jdbc.odbc.JdbcOdbcDriver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;+129
    j java.sql.DriverManager.getConnection(Ljava/lang/String;Ljava/util/Properties;Ljava/lang/ClassLoader;)Ljava/sql/Connection;+154
    j java.sql.DriverManager.getConnection(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/sql/Connection;+41
    j Prosesor.processInput(Ljava/lang/String;)Ljava/lang/String;+51
    j ServerBeritaThread.run()V+35
    v ~StubRoutines::call_stub
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    =>0x02e64358 JavaThread "ServerBeritaThread" [_thread_in_native, id=3508]
    0x02facf38 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1048]
    0x02fadc20 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=2028]
    0x02e61db0 JavaThread "AWT-Windows" daemon [_thread_in_native, id=728]
    0x02e20e48 JavaThread "AWT-Shutdown" [_thread_blocked, id=4056]
    0x009d03c0 JavaThread "CompilerThread0" daemon [_thread_blocked, id=1568]
    0x009cf630 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1572]
    0x009ccba0 JavaThread "Finalizer" daemon [_thread_blocked, id=2580]
    0x009cb818 JavaThread "Reference Handler" daemon [_thread_blocked, id=980]
    0x00035aa8 JavaThread "main" [_thread_in_native, id=1684]
    Other Threads:
    0x00a0b6c0 VMThread [id=1256]
    0x00a0cab8 WatcherThread [id=2276]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    def new generation total 576K, used 43K [0x10010000, 0x100b0000, 0x104f0000)
    eden space 512K, 1% used [0x10010000, 0x10012448, 0x10090000)
    from space 64K, 53% used [0x10090000, 0x10098930, 0x100a0000)
    to space 64K, 0% used [0x100a0000, 0x100a0000, 0x100b0000)
    tenured generation total 1408K, used 665K [0x104f0000, 0x10650000, 0x14010000)
    the space 1408K, 47% used [0x104f0000, 0x105967e8, 0x10596800, 0x10650000)
    compacting perm gen total 4096K, used 4065K [0x14010000, 0x14410000, 0x18010000)
    the space 4096K, 99% used [0x14010000, 0x14408580, 0x14408600, 0x14410000)
    Dynamic libraries:
    0x00400000 - 0x0040b000      C:\java\bin\java.exe
    0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
    0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
    0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
    0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
    0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
    0x08000000 - 0x08144000      C:\java\jre\bin\client\jvm.dll
    0x77d40000 - 0x77dd0000      C:\WINDOWS\system32\USER32.dll
    0x77f10000 - 0x77f56000      C:\WINDOWS\system32\GDI32.dll
    0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
    0x10000000 - 0x10007000      C:\java\jre\bin\hpi.dll
    0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
    0x00390000 - 0x0039e000      C:\java\jre\bin\verify.dll
    0x003b0000 - 0x003c9000      C:\java\jre\bin\java.dll
    0x003d0000 - 0x003de000      C:\java\jre\bin\zip.dll
    0x02e70000 - 0x02f84000      C:\java\jre\bin\awt.dll
    0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
    0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
    0x774e0000 - 0x7761c000      C:\WINDOWS\system32\ole32.dll
    0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\uxtheme.dll
    0x033e0000 - 0x03432000      C:\java\jre\bin\fontmanager.dll
    0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
    0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
    0x73940000 - 0x73a10000      C:\WINDOWS\system32\D3DIM700.DLL
    0x74720000 - 0x7476b000      C:\WINDOWS\system32\MSCTF.dll
    0x035e0000 - 0x035ef000      C:\java\jre\bin\net.dll
    0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
    0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
    0x605d0000 - 0x605d9000      C:\WINDOWS\system32\mslbui.dll
    0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.DLL
    0x20b00000 - 0x20b4b000      C:\WINDOWS\system32\imon.dll
    0x71ad0000 - 0x71ad9000      C:\WINDOWS\system32\WSOCK32.dll
    0x71a50000 - 0x71a8f000      C:\WINDOWS\system32\mswsock.dll
    0x662b0000 - 0x66308000      C:\WINDOWS\system32\hnetcfg.dll
    0x71a90000 - 0x71a98000      C:\WINDOWS\System32\wshtcpip.dll
    0x03710000 - 0x0371c000      C:\java\jre\bin\JdbcOdbc.dll
    0x74320000 - 0x7435d000      C:\WINDOWS\system32\ODBC32.dll
    0x5d090000 - 0x5d127000      C:\WINDOWS\system32\COMCTL32.dll
    0x7c9c0000 - 0x7d1d4000      C:\WINDOWS\system32\SHELL32.dll
    0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
    0x763b0000 - 0x763f9000      C:\WINDOWS\system32\comdlg32.dll
    0x773d0000 - 0x774d2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
    0x20000000 - 0x20017000      C:\WINDOWS\system32\odbcint.dll
    0x77c00000 - 0x77c08000      C:\WINDOWS\system32\VERSION.dll
    0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
    0x5fe80000 - 0x5fe9b000      C:\WINDOWS\system32\odbccp32.dll
    0x77c70000 - 0x77c93000      C:\WINDOWS\system32\msv1_0.dll
    0x76d60000 - 0x76d79000      C:\WINDOWS\system32\iphlpapi.dll
    VM Arguments:
    java_command: ServerBerita
    Launcher Type: SUN_STANDARD
    Environment Variables:
    CLASSPATH=.;C:\PROGRA~1\JMF\lib\sound.jar;C:\PROGRA~1\JMF\lib\jmf.jar;C:\PROGRA~1\JMF\lib;.;.;d:\PROGRA~1\JMF21~1.1E\lib\sound.jar;d:\PROGRA~1\JMF21~1.1E\lib\jmf.jar;d:\PROGRA~1\JMF21~1.1E\lib;
    PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;c:\java\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin;c:\apache\mysql\bin;;C:\PROGRA~1\COMMON~1\MUVEET~1\030625
    USERNAME=acer
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 2, GenuineIntel
    --------------- S Y S T E M ---------------
    OS: Windows XP Build 2600 Service Pack 2
    CPU:total 2 family 6, cmov, cx8, fxsr, mmx, sse, sse2
    Memory: 4k page, physical 1038440k(478648k free), swap 1712796k(1228644k free)
    vm_info: Java HotSpot(TM) Client VM (1.4.2_15-b02) for windows-x86, built on May 22 2007 17:01:47 by "java_re" with MS VC++ 6.0

  • Sql server services give error the remote procedure call failed [0x800706be] in sql server 2008

    sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
    To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
    mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
    but it does not work.
    Plz give the exact soln to solve this error.

    sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
    To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
    mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
    but it does not work.
    Plz give the exact soln to solve this error.
    So when you tried starting SQL server service it gave the error right  ?  or when you click on SQL server services in SQL server configuration manager(SSCM) you get this error. Can you be more clear.  As far as I read your question it has something
    to do with permission. Close SSCM window and this time  right click on SQL server configuration manager and select run as administrator and check if you can see SQL server services
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Obtain Job invoker for a SSIS job scheduled in SQL Server Agent

    Hello,
    I was required to tell the job runner of a particular SSIS job scheduled in SQL Server Agent (in SQL Server Management Studio 2008 R2). I noticed that after running the job, a record can be found in msdb.dbo.sysjobhistory in the [message] columm saying that
    the job is invoked by 'Domain\User'. Is there anyway I can acquire and upload that information into an audit table by adding some additional script into the job? I heard about using token to get job_ID, but what about the actual user name who runs
    the job?
    Thanks

    Just add retry attempts to whatever number you want (2 as per your original explanation) in Job step properties as below
    Have a logic to include a delay of 10 mins . You can make use of WAITFOR function for that
    see
    http://www.mssqltips.com/sqlservertip/1423/create-delays-in-sql-server-processes-to-mimic-user-input/
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Maybe you are looking for