I am trying to run an SSIS Package using sql script. While I try to run this, I am getting the following error message,
"Message Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R)
SQL Server Execute Package Utility Version 12.0.5000.0 for 64-bit
Copyright (C) Microsoft Corporation. All rights reserved. Started:
6:05:54 PM Could not load package "\MSDB\TestPac" because of error
0xC00160AE. Description: Connecting to the Integration Services
service on the computer "Server Name" failed with the following error:
"Access is denied." By default, only administrators have access to
the Integration Services service. On Windows Vista and later, the
process must be running with administrative privileges in order to
connect to the Integration Services service. See the help topic for
information on how to configure access to the service. Source:
Started: 6:05:54 PM Finished: 6:05:54 PM Elapsed: 0.047 seconds.
The package could not be loaded. The step failed."
Related
this is the first time I've tried to schedule a job and I keep getting the error message below. I am using the admin account and checking the 32 bit box. Any ideas on how to remedy? Thanks.
Executed as user: NT Service\SQLAgent$BZMSSQLSERVER. Microsoft (R) SQL
Server Execute Package Utility Version 14.0.2014.14 for 32-bit
Copyright (C) 2017 Microsoft. All rights reserved.
Started: 9:48:28 AM Error: 2019-12-02 09:48:29.50
Code: 0xC0202009
Source: TEST Connection manager "DestinationConnectionExcel"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has
occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft JET Database Engine"
Hresult: 0x80004005 Description: "The Microsoft Jet database engine
cannot open the file ''. It is already opened exclusively by another
user or you need permission to view its data.". End Error
Error: 2019-12-02 09:48:29.50
Code: 0xC00291EC
Source: Preparation SQL Task 1 Execute SQL Task
Description: Failed to acquire connection
"DestinationConnectionExcel". Connection may not be configured
correctly or you may not have the right permissions on this
connection. End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 9:48:28 AM
Finished: 9:48:29 AM Elapsed: 0.641 seconds. The package execution
failed. The step failed.
It may be a permission issue. If you can, change the Agent service account to a Windows AD account with local admin privileges.
I have created an SSIS package in Visual Studio using the SSIS Import and Export Wizard and when I run it there, it runs successfully. Basically, the SSIS package runs a sql query on my SQL Server database and exports the results into an Excel file.
I have wrapped that package into a SQL Server job and scheduled it to run at a specific time. I noticed that it failed and the log file shows the following error messages:
Microsoft (R) SQL Server Execute Package Utility Version 12.0.5000.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 4:44:00 PM Error: 2017-10-12 16:44:00.59 Code: 0xC0016016 Source: ExpExcel Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2017-10-12 16:44:00.68 Code: 0xC0209303 Source: ExpExcel Connection manager "DestinationConnectionExcel" Description: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2017-10-12 16:44:00.68 Code: 0xC00291EC Source: Drop table(s) SQL Task 1 Execute SQL Task Description: Failed to acquire connection "DestinationConnectionExcel". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Error: 2017-10-12 16:44:00.68 Code: 0xC0209303 Source: ExpExcel Connection manager "DestinationConnectionExcel" Description: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2017-10-12 16:44:00.68 Code: 0xC00291EC Source: Preparation SQL Task 1 Execute SQL Task Description: Failed to acquire connection "DestinationConnectionExcel". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:44:00 PM Finished: 4:44:00 PM Elapsed: 0.219 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,,0
I am having a hard time trying to figure out how to debug these errors and finding the solution. If my SSIS package is running fine in Visual Studio (installed on that same machine as SQL Server), then why is it failing as a SQL Server job?
I must also add that Microsoft Office is not installed on that machine. Could that possibly be the cause?
You need to enable 32bit on your SQL Job agent step - And if that doesnt work you need to install OLDB ACE Driver for EXCEL
Driver link:
Microsoft ACE Driver
And as others point out. Your project protection level needs to be the same as the package protection level. You can change that under properties of the package and project.
How to set 32bit on step in SQL Job Agent on step
When you created the package it probably got set up with a User Key protection level. Meaning that any sensitive information (passwords) get encrypted with your user key. By extension, this means only you can really open/run the package. Your best bet (requiring the least amount of effort in my opinion) is to encrypt the package with a password and then you can specific that password as you are creating your SQL Agent job.
I am trying to execute a job from SQL Server Agent however receiving the error:
The login is from an untrusted domain and cannot be used with Windows authentication.
The Sql server 2016 with Sql server Agent and SSIS where a credential account proxy is linking to windows admin account. The proxy is set SSIS package excecution:
The job has only 1 step to run SSIS package. This package is developed/tested/deployed from VS 2016+Data tools.
Here is the step:
and the error:
Right click on the job to view History. Here is the error:
Executed as user: MACHINE_NAME\admin_user. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 2:15:10 PM Failed to execute IS server package because of error 0x80131904. Server: xxx, Package path: \SSISDB\Practise 1\SSIS 1\Package.dtsx, Environment reference Id: NULL. Description: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. Source: .Net SqlClient Data Provider Started: 2:15:10 PM Finished: 2:15:10 PM Elapsed: 0.188 seconds. The package execution failed. The step failed.
The Sql server agent, which is running on the local machine, could not resolve the server name tcp:xxx.cloudapp.azure.com in the step. As the agent is local so just set the server name to .. Resolved.
I have 2 SQL Server instances on my PC, MSSQLSERVER2012 and SQLEXPRESS2014 and both of them were working properly.
But suddenly, both of them stopped and I can't run them again at all.
I get this error:
The request failed or the service did not respond in a timely fashion
I checked tcp/ip setting, even disabled tcp/ip of both instances.
I guessed it might be related to VIA protocol, but I can't see VIA protocol in my configuration manager.
I'll post the error log that SQL Server generates when it failed to start.
2017-05-17 22:24:07.77 Server Microsoft SQL Server 2012 -
11.0.2100.60 (X64) Feb 10 2012 19:39:15 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2
(Build 9200: )
2017-05-17 22:24:07.77 Server (c) Microsoft Corporation.
2017-05-17 22:24:07.77 Server All rights reserved. 2017-05-17
22:24:07.77 Server Server process ID is 6044. 2017-05-17
22:24:07.77 Server System Manufacturer: 'System manufacturer',
System Model: 'System Product Name'. 2017-05-17 22:24:07.77 Server
Authentication mode is MIXED. 2017-05-17 22:24:07.77 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2017-05-17 22:24:07.77
Server The service account is 'WORKGROUP\HAMED-PC$'. This is an
informational message; no user action is required. 2017-05-17
22:24:07.77 Server
Registry startup parameters:
-d C:\Program> Files\Microsoft SQL server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program
Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2017-05-17 22:24:07.77 Server Command Line Startup Parameters:
-s "MSSQLSERVER" 2017-05-17 22:24:07.91 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors
per socket, 4 total logical processors; using 4 logical processors
based on SQL Server licensing. This is an informational message; no
user action is required. 2017-05-17 22:24:07.91 Server SQL Server
is starting at normal priority base (=7). This is an informational
message only. No user action is required. 2017-05-17 22:24:07.91
Server Detected 4087 MB of RAM. This is an informational message;
no user action is required. 2017-05-17 22:24:07.91
Server Using conventional memory in the memory manager.
2017-05-17 22:24:07.94 Server Error: 9694, Severity: 16, State:27.
2017-05-17 22:24:07.94 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for
additional error messages.
2017-05-17 22:24:07.94 Server Error: 9643, Severity: 16, State:1.
2017-05-17 22:24:07.94 Server An error occurred in the Service
Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2017-05-17 22:24:07.94 Server Error: 9694, Severity: 16, State:
30.
2017-05-17 22:24:07.94 Server Could not start Service Broker
manager. Check the SQL Server error log and the Windows error log for
additional error messages.
2017-05-17 22:24:07.94 Server SQL Server Audit failed to record
the SERVER SHUTDOWN action.
Now I will appreciate if someone can help me start my SQL Server instances again
I have the same problem.
Suddenly the services do not work anymore.. I suspect a windows update did this.
Or new group policies that not allow this account to use resources?
Two errors in the Event Viewer:
The SQL Server (SQLEXPRESS) service failed to start due to the
following error: The service did not start due to a logon failure.
And
The MSSQL$SQLEXPRESS service was unable to log on as NT
Service\MSSQL$SQLEXPRESS with the currently configured password due to
the following error: Logon failure: the user has not been granted the
requested logon type at this computer.
Service: MSSQL$SQLEXPRESS
Domain and account: NT Service\MSSQL$SQLEXPRESS
This service account not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this
computer. You can use Local Security Settings (Secpol.msc) to do this.
If this computer is a node in a cluster, check that this user right is
assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account,
and the user right appears to be removed, check with your domain
administrator to find out if a Group Policy object associated with
this node might be removing the right.
Hope this helps to get more information..
A solution I don't trust is removing he password of the user.
Go to Services > SQL Server (SQLEXPRESS) > Properties > Log On > Remove password
But I don't think this solution is a permanent solution.
If you find anything please let me know.
==================================================
Edit 1
We found the reason, my administrator pushed a group policy 'Log on as a service' which overruled my computer users.. and bad things started to happen.
He removed the policy and the original users returned. Everything works again after a 'gpupdate /force' in the command line.
You can find the group policy:
Start > Local Security Policy > Security Settings > Local Policies > User Right Assignment > Log on as a service. If the button 'Add User or Group' is grayed then the Admins are pushing this..
Good luck!
Jonas
I removed old sql server from PC. Then I installed new sql server. After this sql server service doesn't start. When I am running service from sql server config manager - I receive error msg:
"The request failed or the service did not respond in a timely
fashion. Consult the event log or other applicable error logs for
details."
this command: sqlservr.exe -s MSSQL -e C:\1.txt returned logs:
2017-05-09 18:32:55.05 Server Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)
Apr 29 2016 23:23:58
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows 10 Enterprise 6.3 <X64> (Build 10586: )
2017-05-09 18:32:55.05 Server UTC adjustment: 3:00
2017-05-09 18:32:55.05 Server (c) Microsoft Corporation.
2017-05-09 18:32:55.05 Server All rights reserved.
2017-05-09 18:32:55.05 Server Server process ID is 7956.
2017-05-09 18:32:55.05 Server System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X550JX'.
2017-05-09 18:32:55.06 Server Authentication mode is WINDOWS-ONLY.
2017-05-09 18:32:55.06 Server Logging SQL Server messages in file 'C:\1.txt'.
2017-05-09 18:32:55.06 Server The service account is 'USER-PC\User'. This is an informational message; no user action is required.
2017-05-09 18:32:55.06 Server Command Line Startup Parameters:
-s "MSSQL"
-e "C:\1.txt"
2017-05-09 18:32:55.06 Server Error: 17113, Severity: 16, State: 1.
2017-05-09 18:32:55.06 Server Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
2017-05-09 18:32:55.07 Server SQL Server shutdown has been initiated
I tried to add permissions for windows user, local system and local service but it didn't help.
The error log gives you the information about the failure: Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error.
You should check your startup parameters.
Start Configuration Manager -> SQL Server Services -> your instance -> Properties -> Advanced -> Startup Parameters.
It should contain paths to master.mdf, mastlog.ldf and errorlog