I changed the IP server that I have SQL Server on, now all the jobs I wrote on the old IP server, are not running on the new IP server. I get the error
Executed as user: NT SERVICE\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 15.0.2000.5 for 64-bit Copyright(c) 2019 Microsoft. All rights reserved.
Related
Hello we have been working with a remote Server, but this week I am getting error 18456 with status 1, from SQL Server Management Studio when I try to connect from a remote computer.
We are connecting to the Server through a VPN, but we have the correct ports enabled
as you can see in the ping and telnet tests:
ping_test
telnet_test
So there is no issue with it(as far as we know).
We have tried all the suggestions explained in this page:
https://www.liquidweb.com/kb/troubleshooting-microsoft-sql-server-error-18456-login-failed-user/
(And almost all different blogs/forums found with this error and remote connection errors)
protocol_properties_ip
protocol_properties_ip_tab
(We also have tried changing to Yes Enabled property under IP1 with same results)
IPALL seems to be right. (According to recommendations in forums)
protocol_properties_ip_tab_2
Remote connections are allowed:
connection_settings
Security settings are as expected (SQL Server and Windows Authentication mode):
Security_settings
We have checked all this stuff but we still unable to connect remotely.
SQL Server info:
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
We have been working with the server ok until this week (the server it isn't ours, it is from a customer), we don't know what changed this week, I hope you can give me more ideas to check and solve this issue.
I have a fresh instance of SQL Sever 2017,
Microsoft SQL Server 2017 (RTM-GDR) (KB4505224) - 14.0.2027.2 (X64) Jun 15 2019 00:26:19 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
And v17.9.1 of SSMS. When I try to connect to the Integration Service I am receiving the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to sqlprod.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
Connecting to the Integration Services service on the computer "sqlprod" failed with the following error: "The specified service does not exist as an installed service.".
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.
For help, click: http://go.microsoft.com/fwlink/?LinkId=506689
------------------------------
Connecting to the Integration Services service on the computer "sqlprod" failed with the following error: "The specified service does not exist as an installed service.".
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.
------------------------------
BUTTONS:
OK
------------------------------
Why is my connection failing and why does it think it's a 2005 instance?
Also, here's my SSMS info:
You should get the SSMS version 16 from https://learn.microsoft.com/en-us/sql/ssms/previous-sql-server-management-studio-releases install and connect to Integration Services instance.
BTW, this connection is kept for compatibility reasons with SSIS 2005-2008 packages. Starting from MS SQL 2012, SSIS supports so called Integration Catalogue, fully manageable from SSMS Database connection.
Our office does not have SQL Server agent installed and when I run SQLCMD command it gave me an error as shown below?
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft
Corporation. All rights reserved.
C:\Users\c98035>sqlcmd
Sqlcmd: Error: Microsoft SQL Server Native
Client 11.0 : Named Pipes Provider: Could not open a connection to SQL
Server [2]
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout
expired.
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : A
network-related or in stance-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.
Can someone help me to tell me another way or if you can help me fix the error above so I can use SQLCMD.
I have the following error while I connect to SQL Server 2008 Management Studio with Windows authentication.
"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."
the errorlog file::
2018-01-15 10:43:43.58 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition on Windows NT 6.2 <X64> (Build 9200: ) (WOW64)
2018-01-15 10:43:43.61 Server (c) 2005 Microsoft Corporation.
2018-01-15 10:43:43.61 Server All rights reserved.
2018-01-15 10:43:43.61 Server Server process ID is 16684.
2018-01-15 10:43:43.61 Server System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 5040'.
2018-01-15 10:43:43.61 Server Authentication mode is WINDOWS-ONLY.
2018-01-15 10:43:43.61 Server Logging SQL Server messages in file 'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BDMS\MSSQL\Log\ERRORLOG'.
2018-01-15 10:43:43.61 Server This instance of SQL Server last reported using a process ID of 3304 at 12/01/2018 3:52:56 PM (local) 12/01/2018 2:52:56 PM (UTC). This is an informational message only; no user action is required.
2018-01-15 10:43:43.61 Server Registry startup parameters:
-d c:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BDMS\MSSQL\DATA\master.mdf
-e c:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BDMS\MSSQL\Log\ERRORLOG
-l c:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BDMS\MSSQL\DATA\mastlog.ldf
2018-01-15 10:43:43.66 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-15 10:43:43.66 Server Detected 8 CPUs. This is an informational message; no user action is required.
2018-01-15 10:46:22.60 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-01-15 10:46:22.63 Server Node configuration: node 0: CPU mask: 0x000000ff Active CPU mask: 0x000000ff. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-01-15 10:49:50.06 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
Operating System : Windows 8
Visual Studio installed : 2015 Enterprise Edition
Installed successfully : SQL Server 2008 R2
Installed successfully : SQL server management studio
But while checking the services through SQL configuration manager cannot see the instance server :
"remote procedure call failed"
This can happen if you have more than once instance of SQL installed, I've seen it happen where Express has also been installed on the server.
Browse directly to the correct version of configuration manager here:
SQL Server 2016 - C:\Windows\SysWOW64\SQLServerManager13.msc
SQL Server 2014 - C:\Windows\SysWOW64\SQLServerManager12.msc
SQL Server 2012 - C:\Windows\SysWOW64\SQLServerManager11.msc
SQL Server 2008 - C:\Windows\SysWOW64\SQLServerManager10.msc