SSIS Package No longer runs after changing Service to Domain user

Hello, 
I changed the SQL Agent/SQL Service owner on our SQL 2008r2 Server and one of the jobs started to fail with the following message:
"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An OLE DB record is available.  Source:
"Microsoft Office Access Database Engine"  Hresult: 0x80004005  Description: "Unexpected error from external database driver (????????).".  End Error  Error: 2014-05-30 14:47:18.68     Code: 0xC020801C    
Source: Upload Source - Page1_1$ [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER."
The AcquireConnection method call to the connection manager "test.xlsx" failed with error code 0xC0202009.  There may be error messages posted before this with more information
on why the AcquireConnection method call failed.  
The user running the service has local admin rights on the server and all of the other jobs are still running successfully. I can also export the package and run it without issue. Its only when its ran through a schedule/job agent that it fails. Any tips
would be great as i need to get this running yet today. 
Thanks!
Eric 

Hi Eric,
According to your description, the issue occurred after the job owner was changed. I suggest that you create a new job to run the package to see if the issue persists. If the issue doesn’t occur in a new job, the issue should be related to the operations
of changing job owner.
If the issue persists in a new job, the error message generallys occurs due to the Microsoft ACE OLE DB Provider 12.0. If you check the “Use 32 bit runtime” option to make the package run in 32-bit runtime mode, make sure the 32-bit Microsoft ACE OLE DB
Provider is installed on the server. If the  “Use 32 bit runtime” option is not checked, you need to install the 64-bit Microsoft ACE OLE DB Provider. You can get the appropriate version of Microsoft ACE OLE DB Provider from:
http://www.microsoft.com/en-in/download/details.aspx?id=13255 
If the Microsoft ACE OLE DB Provider 12.0 version correctly matches the package runtime mode, try to reinstall the Microsoft ACE OLE DB Provider. Moreover, the AccessDatabaseEngine.exe and AccessDatabaseEngine_x64.exe cannot be installed side by side.
Regards,
Mike Yin
TechNet Community Support

Similar Messages

  • SSIS Package will only run as SQL Agent Job when I have remote desktop to server open.

    Hey guys, so I have another problem to add to the already massive 'SSIS/SQL Server Agent Job' pile. After days of searching, I can't seem to find anything specific to my problem though.
    The setup is as follows: a SSIS package that refreshes and saves excel files that are hosted on a server. The package runs fine on the local machine, using BIDS on the server, and will even work as a SQL Agent Job on the server IF there is a remote
    desktop connection to the server. To elaborate, if I simply run the job as you would normally do it will fail and give the below error. If I run the job while either myself, or a different machine, has a remote desktop connection to the server where the
    job is scheduled - it will run successfully.
    Below is the error from the History File of the job. Any help would be greatly appreciated.
      Source: Refresh Excel and Save      Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x8000401A): Retrieving
    the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 8000401a.     at ST_79772452677f4de1852d5ffbba3e5232.csproj.ScriptMain.ExcelRefresh(String FileName)    
    at ST_79772452677f4de1852d5ffbba3e5232.csproj.ScriptMain.Main()     --- End of inner exception stack trace ---     at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct&
    sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)     at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)    
    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)     at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
    invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)     at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo
    culture, String[] namedParams)     at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)     at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
    UPDATE:
    In my previous post the Identity in DCOM Config file for Microsoft Excel was set as The Interactive User. The job was working only when I had a remote connection to the server open.
    If I set the Identity to 'This User' and use the username and password of the server login account, it will work as a scheduled job without needing an open remote connection to the server. So it works, great! but I have reservations setting this
    for all instances of Excel for the server. I'm sure other users have different accounts they use for running Excel. Any suggestions around this?

    Hi LiamSexton,
    It should be the server-side Automation of Office issue described in the following KB article:
    http://support.microsoft.com/kb/257757 
    Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit
    unstable behavior and/or deadlock when Office is run in this environment.
    User Identity: Office applications assume a user identity when the applications are run, even when Automation starts the applications. The applications try to initialize toolbars, menus, options, printers, and some add-ins based on settings in the user
    registry hive for the user who launches the application. Many services run under accounts that have no user profiles (such as the SYSTEM account or the IWAM_[servername] accounts). Therefore, Office may not initialize correctly on startup. In this situation,
    Office returns an error on the CreateObject function or the CoCreateInstance function. Even if the Office application can be started, other functions may not work correctly if no user profile exists.
    To work around the issue, you can refer to the following alternative introduced in the article:
    Most server-side Automation tasks involve document creation or editing. Office 2007 supports new Open XML file formats that let developers create, edit, read, and transform file content on the server side. These file formats use the System.IO.Package.IO
    namespace in the Microsoft .NET 3.x Framework to edit Office files without using the Office client applications themselves. This is the recommended and supported method for handling changes to Office files from a service.
    Regards,
    Mike Yin
    TechNet Community Support

  • Erorr calling long running sync web service

    Hello
    I have definied simple async process:
    assign (from process input to ws invoke input)
    sync ws invoke
    assign (from ws invoke output to process output)
    Sync Web Service is long running (few minutes). In order to avoid timeout I have accordingly set sync-max-wait-time property.
    I have observed that after starting process instance I can't see it in BPEL Console (however I know it is working). Furthermore when invoke activity ends (so instance state must be saved in database) I can see following error on system console:
    <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Cannot ins
    ert audit trail.
    The process domain was unable to insert the current log entries for the instance
    "2314" to the audit trail table. The exception reported is: RollbackException:
    The transaction has been marked for rollback (timed out)
    Please check that the machine hosting the datasource is physically connected to
    the network. Otherwise, check that the datasource connection parameters (user/p
    assword) is currently valid.
    sql statement: INSERT INTO audit_trail ( cikey, domain_ref, count_id, log ) VALU
    ES ( ?, ?, ?, ? )
    <2005-01-06 13:14:10,268> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseSc
    heduledWorker::process> Failed to handle dispatch message invoke instance messag
    e 0c92305db480f36d:149b290:10147dc1b2e:-7fd6 ... exception Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.
    engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transac
    tion was rolled back: timed out; nested exception is: java.rmi.RemoteException:
    No Exception - originate from:java.lang.Exception: No Exception - originate from
    :; nested exception is:
    java.lang.Exception: No Exception - originate from:
    Best Regards

    Hi,
    There are 2 ways to work around the error that you are seeing.
    Option #1: increase the JTA timeout of the underlying application server.
    Option #2: in the bpel.xml of your process, add a "nonBlockingInvoke" property to the partnerLink representing the interaction with the long running service.
    Option #2 should also address the fact that the instance is not visible in the bpel console.
    Edwin

  • Intermittently my SSIS Packages which are run through the JOB are failing

    Hi SSIS Guru's,
    I am facing a very strange problem.
    We have 2 Physical Servers (A and B) on which we have installed the SQL Server, one primary (A) and other as secondary (B). And there is a cluster (C) available to acces the running server. I have created some SSIS packages which we installed on the Server A (Primary), and created the job on the cluster server which initiates the SSIS packages, whcih are installed in the File System.
    The problem i am facing is the some thing related to Connection time out. And interestingly i am not getting this error Always. Approxiamtely For Every 5 Times once it;s Failing. I am copying the errors Which i encountered in the different runs.
    The thing i am confused is why i am not geting the error all the time? And Why am i getting this error all the time in a different data flow task. My SSIS Package structure is I have created one master package and 6 Child packages. I am getting the connection string for the Data base from the Configuration file which is defined in the XML File.
    The connection string that i am using is
    Data Source=<<server name>>;User ID=DOMAIN\user;Initial Catalog=DatabaseName;Provider=SQLNCLI.1;Integrated Security=SSPI;
    RUN 1 - Error
    Executed as user: AMR\sys_calyp. ...sion 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights
    reserved.    Started:  2:00:07 PM  Error: 2007-09-15 14:02:35.92     Code: 0xC0202009     Source: ssis_emp Connection manager
    "DBCONNECTION"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An
    OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Unable to complete
    login process due to delay in opening server connection".  End Error  Error: 2007-09-15 14:02:35.92     Code: 0xC020801C    
    Source: infr_char Get the Records from emp 1 [72]     Description: SSIS Error Code
    DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "DBCONNECTION" failed with error code 0xC0202009.  There may be error messages posted before this with more information on
    why the AcquireConnection method...  The package execution fa...  The step failed.
    RUN 2 - Error
    Message
    Executed as user: AMR\sys_calyp. ...sion 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights
    reserved.    Started:  9:15:01 AM  Error: 2007-09-15 09:17:01.64     Code: 0xC0202009     Source: ssis_emp Connection manager
    "DBCONNECTION"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An
    OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Unable to complete
    login process due to delay in opening server connection".  End Error  Error: 2007-09-15 09:17:01.64     Code: 0xC020801C    
    Source: Data Flow Task Get the Records from emp [473]     Description: SSIS Error Code
    DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "DBCONNECTION" failed with error code 0xC0202009.  There may be error messages posted before this with more information on
    why the AcquireConnection me...  The package execution fa...  The step failed.
    Run -3 Error
    Message
    Executed as user: AMR\sys_calyp. ...sion 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights
    reserved.    Started:  11:30:01 PM  Error: 2007-09-14 23:32:21.28     Code: 0xC0202009     Source: ssis_dept Connection
    manager "DBCONNECTION"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code:
    0x80004005.  An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Unable
    to complete login process due to delay in opening server connection".  End Error  Error: 2007-09-14 23:32:21.28     Code:
    0xC020801C     Source: Data Flow Task Get the Records from dept [632]     Description: SSIS Error Code
    DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "DBCONNECTION" failed with error code 0xC0202009.  There may be error messages posted before this with more information on
    why the AcquireConnection method ...  The package execution fa...  The step failed.
    Run - 4 Error
    Message
    Executed as user: AMR\sys_calyp. ...sion 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights
    reserved.    Started:  11:00:02 PM  Error: 2007-09-14 23:02:21.46     Code: 0xC0202009     Source: ssis_emp Connection
    manager "DBCONNECTION"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code:
    0x80004005.  An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Unable
    to complete login process due to delay in opening server connection".  End Error  Error: 2007-09-14 23:02:21.46     Code:
    0xC020801C     Source: infr_itm_char_val Get the Records from emp_master [1]     Description: SSIS Error Code
    DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "DBCONNECTION" failed with error code 0xC0202009.  There may be error messages posted before this with more information on
    why the AcquireCon...  The package execution fa...  The step failed.
    Run -5 Error
    Message
    Executed as user: AMR\sys_calyp. ...Execute Package Utility  Version 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp
    1984-2005. All rights reserved.    Started:  9:10:59 PM  Error: 2007-09-14 21:12:23.25     Code: 0xC0202009     Source:
    ssis_salgrade Connection manager "DBCONNECTION"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred.
    Error code: 0x80004005.  An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005 
    Description: "Unable to complete login process due to delay in opening server connection".  End Error  Error: 2007-09-14
    21:12:23.25     Code: 0xC020801C     Source: Data Flow Task - ssis_salgrade get salgrade [3227]     Description: SSIS Error
    Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "DBCONNECTION" failed with error code 0xC0202009.  There may be error messages posted before this with more information on
    why the AcquireConnection method c.  The step failed.

    I thought i found the solution my self... I changed the delay validation to all the packages to true and the problem dissappeared

  • Package fails first time after changes

    Hi,
    I have a package that I am making changes to. I'm running the package via the SQL Plus Worksheet. After making the changes to the package and recompiling, I try to execute the program from SQL Plus Worksheet and get this error message:
    BEGIN xml_import_export_package2_NED.start_transfer(:v_error_no, :v_error_message,:v_error_procedure); END;
    ERROR at line 1:
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "AVENTISDM.XML_IMPORT_EXPORT_PACKAGE2_NED" has been invalidated
    ORA-04065: not executed, altered or dropped package "AVENTISDM.XML_IMPORT_EXPORT_PACKAGE2_NED"
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    The package does not run. However, when I execute it again it works fine. I'm now concerned that if I make a change to a package during the day, that is scheduled to run at night, that it will fail unless I run it once first.
    Is this behaviour by design?
    Regards,
    Ned

    This behaviour is by design, but it should not be a problem for your scheduled job.
    When you run the package in sqlplus, the package is loaded into SGA, and a pointer to this area is in your PGA. When you re-compile the package, the copy in SGA is invalidated. When you then try to re-run the package, the invalid pointer causes the error. Running it the second time causes a re-load of the package and the re-creation of the pointer. However, a new session (which your scheduled job would have) would not have the invalid pointer, so would work correctly.
    John

  • SharePoint farm - SQL Server - MSSQLSERVER service is running as "Local System" - Can I change it to Domain User account?

    Hi there,
    In my SharePoint 2010 farm - on the SQL Server:
    The MSSQLSERVER service is running under Local System.
    1. Can I change it to run as a normal Domain User account?
    2. Does it need any extra privileges?
    3. Is it a safe thing to do?
    Brief description will be very useful.
    Thanks so much.

    You need to create Service account with password never expire option+ User never change password
    Then you need to go through below recommendation from Microsoft
    Security Considerations for a SQL Server Installation
    Planning for Services, Accounts, and Connections
    Hope you got starting point
    Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply.

  • Server0 not statring after change od password for user sapjsf

    Hi
    I had to change password of  sapjsf user,after which i am not able to start server0.
    Please help me how to get server0 started.
    std_server0.out*****************
    <verbosegc version="200804_28">
    Loading services.:
      Service memory started. (104 ms).
      Service runtimeinfo started. (39 ms).
      Service timeout started. (94 ms).
      Service cross started. (106 ms).
      Service file started. (130 ms).
      Service trex.service started. (187 ms).
      Service userstore started. (30 ms).
      Service jmx_notification started. (40 ms).
      Service p4 started. (203 ms).
      Service classpath_resolver started. (64 ms).
      Service deploy started. (8442 ms).
      Service MigrationService started. (36 ms).
      Service bimmrdeployer started. (6 ms).
      Service log_configurator started. (11037 ms).
      Service locking started. (4 ms).
      Service http started. (237 ms).
      Service naming started. (580 ms).
      Service failover started. (63 ms).
      Service appclient started. (93 ms).
      Service javamail started. (135 ms).
      Service ts started. (125 ms).
      Service jmsconnector started. (175 ms).
      Service licensing started. (34 ms).
      Service connector started. (219 ms).
      Service configuration started. (48 ms).
      Service iiop started. (334 ms).
      Service webservices started. (653 ms).
      Service dbpool started. (1857 ms).
    Oct 26, 2008 2:23:19 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_94] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=$$
      client=100
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    Oct 26, 2008 2:23:19 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_94] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
            ... 6 more
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Oct 26, 2008 2:23:19 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_94] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

    There are lots of posts on this issue on the form. Update the password in the parameter, server->services->UME provider-> ume.r3.connection.master.passwd using configtool.

  • BSOD when starting MSMQ service as domain user Windows server 2012

    Hi
    We have a problem with a server getting BSOD when we start a service related to MSMQ. We get the attempted execute of noexecute memory BSOD whenever we start the service as a User on the domain. When we start the service as a system local it starts without
    problem. I got the crashdump here:
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\170\120314-11828-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 9200.16912.amd64fre.win8_gdr.140502-1507
    Machine Name:
    Kernel base = 0xfffff800`48476000 PsLoadedModuleList = 0xfffff800`48742aa0
    Debug session time: Wed Dec  3 14:41:01.892 2014 (UTC + 1:00)
    System Uptime: 0 days 0:04:09.904
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck FC, {7f982e340e0, 791000010fdb1025, fffff8800485a5e0, 80000005}
    Probably caused by : mqac.sys ( mqac!ACCreateQueue+a77 )
    Followup: MachineOwner
    1: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: 000007f982e340e0, Virtual address for the attempted execute.
    Arg2: 791000010fdb1025, PTE contents.
    Arg3: fffff8800485a5e0, (reserved)
    Arg4: 0000000080000005, (reserved)
    Debugging Details:
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  mqsvc.exe
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    TRAP_FRAME:  fffff8800485a5e0 -- (.trap 0xfffff8800485a5e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000007f982e0c950 rbx=0000000000000000 rcx=0000005dff1fecd0
    rdx=0000005dff34e988 rsi=0000000000000000 rdi=0000000000000000
    rip=000007f982e340e0 rsp=fffff8800485a778 rbp=fffff8800485ab80
     r8=fffffa800e623980  r9=0000000000000521 r10=fffffa800ec547a0
    r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    000007f9`82e340e0 ??              ???
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80048661ef1 to fffff800484d0540
    STACK_TEXT:  
    fffff880`0485a408 fffff800`48661ef1 : 00000000`000000fc 000007f9`82e340e0 79100001`0fdb1025 fffff880`0485a5e0 : nt!KeBugCheckEx
    fffff880`0485a410 fffff800`48588980 : fffff880`0485a5e0 ffffd8e9`9e6056e2 fffffa80`0ec547a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33f2d
    fffff880`0485a450 fffff800`4850aabd : fffff880`0485a500 00000000`c0000016 fffffa80`0e603b00 fffffa80`0e623980 : nt! ?? ::FNODOBFM::`string'+0x33e85
    fffff880`0485a4a0 fffff800`484cdfee : 00000000`00000008 00000000`00000000 00000000`00000000 fffff880`0485a5e0 : nt!MmAccessFault+0x3ed
    fffff880`0485a5e0 000007f9`82e340e0 : fffff880`00dc5297 fffffa80`0ec54770 00000000`00000000 fffff8a0`011ce7c0 : nt!KiPageFault+0x16e
    fffff880`0485a778 fffff880`00dc5297 : fffffa80`0ec54770 00000000`00000000 fffff8a0`011ce7c0 fffff980`00000000 : 0x000007f9`82e340e0
    fffff880`0485a780 fffff880`00dc60d7 : 00000000`00000000 0000005d`ff34e988 00000000`00000000 00000000`00000000 : mqac!ACCreateQueue+0xa77
    fffff880`0485a7f0 fffff800`488ab127 : fffffa80`0e5ed520 fffffa80`0d50ecf0 00000000`00000521 00000000`00000000 : mqac!ACDeviceControl+0x62b
    fffff880`0485a890 fffff800`488c02f6 : 00000000`00000000 fffff8a0`00000080 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x7e5
    fffff880`0485aa20 fffff800`484cf553 : 00000000`00000000 00000000`0000000c fffff6fb`7dbed078 fffff6fb`7da0ff30 : nt!NtDeviceIoControlFile+0x56
    fffff880`0485aa90 000007f9`8a702c1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    0000005d`ff34e928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007f9`8a702c1a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    mqac!ACCreateQueue+a77
    fffff880`00dc5297 85c0            test    eax,eax
    SYMBOL_STACK_INDEX:  6
    SYMBOL_NAME:  mqac!ACCreateQueue+a77
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: mqac
    IMAGE_NAME:  mqac.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5010abc2
    IMAGE_VERSION:  6.2.9200.16384
    BUCKET_ID_FUNC_OFFSET:  a77
    FAILURE_BUCKET_ID:  0xFC_mqac!ACCreateQueue
    BUCKET_ID:  0xFC_mqac!ACCreateQueue
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0xfc_mqac!accreatequeue
    FAILURE_ID_HASH:  {d1daca31-6256-358c-65b5-69af54392880}
    Followup: MachineOwner

    Hi,
    For BugCheck FC, it indicates that an attempt was made to execute non-executable memory. For more details,
    please refer to following article.
    Bug Check 0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    à
    whenever we start the service as a User on the domain
    . When we start the service as a system local it starts without problem
    Did you mean that just use a standard domain user account to start the service, then encounter the issue? If
    configure Log on as Local System account, will no BSOD issue occurred? Just a confirmation, thanks for your understanding.
    Please check if you install all necessary Windows Updates on the server.
    In addition, as you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. However, it is
    not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Hope this helps.
    Best regards,
    Justin Gu

  • SDK service using domain user trying to set SPN for computer account

    I have a SDK service running under a domain user account, but it tries to register the SPN for the computer account of the machine?!
    Therefore I get the following alert: 
    The System Center Data Access service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/WIN-9IAJC0HS9RJ and MSOMSdkSvc/WIN-9IAJC0HS9RJ.domainxx.local to the servicePrincipalName of CN=WIN-9IAJC0HS9RJ,CN=Computers,DC=domainxx,DC=local
    Which makes sense because it has not the permissions to do that.
    When I make the domain user account member of domain admins it has the concerning permissions and it indeed registers that SPN to the computer account. But why?? The SPN should be registered to the domain user account instead (and therefore I had given the
    domain user account the read/write permissions to itself to do that).
    I have the following SPN registered now for the computer and domain user account:
    setspn -l WIN-9IAJC0HS9RJ
    Registered ServicePrincipalNames for CN=WIN-9IAJC0HS9RJ,CN=Computers,DC=domainxx
    DC=local:
            MSOMSdkSvc/WIN-9IAJC0HS9RJ
            MSOMSdkSvc/WIN-9IAJC0HS9RJ.domainxx.local
            MSOMHSvc/WIN-9IAJC0HS9RJ
            MSOMHSvc/WIN-9IAJC0HS9RJ.domainxx.local
            TERMSRV/WIN-9IAJC0HS9RJ
            TERMSRV/WIN-9IAJC0HS9RJ.domainxx.local
            WSMAN/WIN-9IAJC0HS9RJ
            WSMAN/WIN-9IAJC0HS9RJ.domainxx.local
            RestrictedKrbHost/WIN-9IAJC0HS9RJ
            HOST/WIN-9IAJC0HS9RJ
            RestrictedKrbHost/WIN-9IAJC0HS9RJ.domainxx.local
            HOST/WIN-9IAJC0HS9RJ.domainxx.local
    setspn -l domainxx\omdas
    Registered ServicePrincipalNames for CN=OMDAS,CN=Users,DC=domainxx,DC=local:
    none for this account
    I don't get it. Anyone?
    I am using SCOM 2012 R2
    Pls help.
    Thanx in advance.
    Regards
    Chris

    SCOM SDK service really tries to set its SPN to the computer account (although the SDK service is running using a domain user account). The alert is no bug!
    I know this for sure because I gave the SDK service permission to do it - by making the domain user account member of the domain admins security group - and it indeed sets the SPN on the computer account.
    The latter is the actual bug I would say! It should try to set the SPN for the domain user account the sdk service is running with.
    Then again, nog having the SPN been set correctly to this domain user account, does not seem to bother SCOM at all indeed. Perhaps it uses NTLM instead in this scenario.
    Can anyone comfirm?

  • SSIS package not working on 2012 Integration Service Catalog deployment

    I've set up a package that imports data from an excel spreadsheet(my only possible data source).  I deployed it and it worked for a while and then broke.  I had to switch to a generated connection string for excel with IMEX=1 to make things work.
      Now it works fine on from Visual Studio on my local machine, but when I run it from Integration Services I get:
    "The external column "<COLUMN NAME>" needs to be updated, for every column in the spreadsheet.   I am using the same excel file on my local machine as on the other machine.
    Why can't I get it to work when it's deployed to the SSIS Server?

    Hi,
    Excel files are a bit tricky to work with. Any small change in data type, metadata can make your package fail.
    I have had such experience earlier. The file contents, columns everything was same but it used to fail with same metadata issue.
    Here is what helped me:
    1. I tried to clear all formatting using the excel formatting options and it worked for me. But we can't ask the users to do all these things manually before uploading files to the application.
    2. So, I created a new excel file and created all column headers manually. Please make sure don't copy paste from any other excel file otherwise formatting and metadata will get changed.
    3. Once you have the template ready. Configure your package Excel columns according to the template.
    4. Now, If you copy and paste data into this plain formatting free file, data will adapt the template settings and won't give the metadata errors.
    5. We uploaded the same template on our application and users created the data in same template which resolved the issue for us.
    CSVs on the other hand don't have any such issues.
    Hope this helps. Good Luck!

  • Soa managed server is not running after changing weblogic admin password

    hi guys....
    we have oim 11g deployment on weblogic 10.3.5 ....it was working fine....
    we changed the weblogic user password through admin console and changed the boot.properties file also....after that we succcessfully started the adminserver but soa server is not starting and giving following errors...
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         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:597)
         at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         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:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy28.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         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:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy46.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Regards
    jdev

    Which boot.properties did you update Just the admin server? You need to update this file on each of the servers in the domain. Browse to the soa server directory inside the domain directory and there inside the security directory you should see the boot.properties file. You need to update the password in this file.
    -Bikash

  • HTML eMail no longer works after change from 8100 to 8310

    Hello all,
    I have a Pearl 8100, which I upgraded successfully to version 4.5. Then I could receive and read HTML eMail, very nice.
    Now I got a Curve 8310 which I also upgraded to 4.5 supporting HTML eMail. In BIS I changed the PIN and IMEI numbers and the new device was registered.
    Now when I set eMail format to HTML and receive an HTML eMail, it only shows some lines (in nice new HTML) or even nothing and a hint, that more data is available with the number of bytes left. If I select the "More" option on the device, a transfer of data starts, showing that the Curve receives more data. Then the More-Data-Hint shows that only still one byte more is available, but the message still looks the same, showing only the first lines or even nothing. Repeating getting more data does not help. Seems the device has some problem parsing the data.
    What I already tried:
    - Hard reset of the device
    - Delete all service books
    - Resend service books from BIS
    - Enable/Disable HTML mail on device
    None of them helped.
    Network is German Vodafone. Both devices (Pearl and Curve) run Vodafone software.
    By the way: If I switch to text mode, I can see the whole message, but of course unformatted in the old format. Switching back to HTML again shows only part of the message or nothing.
    Does anyone have an idea what happened? Or who can I ask? There is no support hotline for private people on blackberry site.
    Thanks in advance.
    Joerg.
    Solved!
    Go to Solution.

    You can't delete the whole account, just the BIS email accounts.
    In this order, After deleting them, also delete the service books on your BB. 
    Reboot the BB, (battery out, replace and reboot).
    Look and confirm the SBs are gone.
    Now, reset up the email accounts in the BIS, and send the SBs again if needed.
    You should get new registration messages on the BB... and you might need to do a battery bpull reboot again.
    This process, in this order, will assure you get the NEW service books, rather than just writing over old ones.
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • SSIS package issues when running as a regular user

    Hello
    I have one package which is getting data from MSSQL server and putting it to the excel (2007 format).
    When started as an administrator from Visual studio, IS, command line or SQL Agent job it works just fine.
    But when using regular user (SSIS proxy in SQL Agent job) it does not return any errors, but result Excel file is just empty. It puts only firs row with headers into it.
    Only difference I've found when executing as admin and regular user is a warning in package execution detailed log:
    OnWarning,SERVERNAME,USERNAME,PACKAGE_NAME,{GUID},{GUID},2014.03.21 15:23:22,2014.03.21 15:23:22,-2147183868,0x,Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available.  To resolve,
    run this package as an administrator, or on the system's console.
    If I add user to local administrators group it runs just fine.
    Trying to search the web I've found that most causes of thet could be UAC enabled on the server. But it is not enabled.
    SQLserver - Microsoft SQL Server 2012 - 11.0.2383.0 (X64)
    Windows Server 2008 R2
    Thanks in advance,
    Olegas

    It could be also an issue with the access to the %temp% directory.
    But I suggest again, you do not rely on turning the logging on that is built into DTEXEC, you need to provide this package right now with thorough logging to find the root cause of the issue. E.g. no access to a shared drive may an issue, too.
    Arthur My Blog

  • SSIS package takes longer time when inserting data into temp tables

    querying records from one  server  and  inserting them into temp tables is taking longer time.
    are there any setting in package which  enhance the performance .

    will local temp table (#temp ) enhance the performance  ..
    If you're planning to use # tables in ssis make sure you read this
    http://consultingblogs.emc.com/jamiethomson/archive/2006/11/19/SSIS_3A00_-Using-temporary-tables.aspx
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Lightroom: Why does auto white balance no longer work after changing the camera calibration profile?

    I'm using NEF raw files from Nikon.
    Lets say for example I import a NEF file into Lightroom (v4) and click on 'auto' for white balance. The white balance in the image is  adjusted correctly (somewhat). However, if I then change the camera profile (in the camera calibration section) from 'adobe standard' to 'camera standard' then the white balance in the image becomes very wrong. I then have to set the white balance back to 'as shot' and correct it manually instead.
    Why would 'auto white balance' no longer work just because I change the profile from 'adobe standard' to 'camera standard'?
    Any ideas?

    Works as expected here...
    Which Lr version and what OS??

Maybe you are looking for