I have a script task that needs to connect to both DB2 on LUW and DB2 on Z/OS. My understanding is that within the script task I should use an ADO.NET Connection manager.
This I have done for the DB2 on LUW connection using the Microsoft OLE DB Provider for DB2 and can connect just fine. Using that as a guide I am trying to create a connection manager for DB2 mainframe, almost identical except for server name / port number and DBMS platform properties. I've tried every which way to get a connection to Db2 on Z/OS and wind up with an error "Test connection failed because of an error in initializing provider. The request for the host resource failed."
I can define an OLEDB connection manager and connect via its "test connection" but cannot use in script task.
Any thoughtss most welcome,
Phil Jackson
Related
I'm trying to create a SSAS Project and deploy to a remote server.
The Data Source is a Database in the same server, but the project must be made in my laptop.
The remote server is not in a domain environment, so to login in SSAS, I used runas /netonly mothod using Server's Administrator Account, which works fine to connect to SSAS Server through SSMS.
I created SSAS Project using Workspace Server and connection is successful.
I am also able to connect to same Server using SQL Server Database Data Source, using Impersonate Service Account, but after I select the tables I need, the processing fails and gives me this Error:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataSource.Error] Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.).
And as result I get all tables without data, just column names.
If I create a project using Integrated Workspace, I am able to get Data from Source, but the same Error occurs when I try to Deploy the Project. The metadata deploys successfully, but all processing fails with the same Error.
I tried to Increase Timeout, but the same thing happens even after waiting 30 minutes.
This process does not fail if I create and execute the project inside the Server.
Enable the TCP/IP in both Server NetWork and Client protocols;
Set TCP port:1433;
And then try it again.
Please reference this: troubleshoot-connecting-to-the-sql-server-database-engine
I'm trying to utilize Neo4j ETL Tool to Import Data From My SQL Server Database into the Neo4j Graph Database. I also enabled TCP/IP 1433 Port in SQL Server 2019 Configuration Manager and Authorized it by Firewall and Imported Suitable mssql-jdbc-8.2.2.jre8 file for JDBC Driver option.
I already set
Connection name: test
Host:localhost
Type: MSSQL
Database: my_database_name
Schema: my_db_schema
and here is my connection URL:
jdbc:sqlserver://localhost:1433;databaseName=TSQLV4
I set all of the options fines but When I aim to Test and Save the connection I encounter with this weird error:
Connection failed. SQL state: S0001, message: Login failed for user ''. ClientConnectionId:33b259b2-650a-4017-94fa-b86cfc657c9e
and My SQL Server Services are all run in the background among them:
MSSQLSERVER
MSSQLSERVER Agent
MSSQLSERVER VSS Writer
do you have any idea to run the job?
If you did not create any user in TSQLV4 database, just put the intergratedSecurity=true at the end of your jdbc connection string like below:
jdbc:sqlserver://localhost:1433;databaseName=TSQLV4;integratedSecurity=true;
I have scoured high and low for a solution but nothing has helped. To be clear, I am not developing a SSIS package, I am simply trying to run one that has already proven to work. This issue is server specific.
We have an ETL Job that builds a repository from a production database for reporting purposes. I built a new VM server with bigger resources to ease the burden of this process on our larger databases.
Server is Windows Server 2012R2. Running SQL Server 2014 SP2 CU05 with integration services and really not much else. This job runs through the agent on 15 minute intervals. The first few times it runs, it does actually start building some of the data in the destination database, but this error persists with every new batch that is executed, whether manually or on schedule, and after a while it just stops moving data.
Here is the base error:
SSIS Error Code DTS_E_CANNOTACQVIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ETL_Framework" failed with error code 0xCO202009.
There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Said error messages before the AcquireConnection call:
SSIS Error Code DTS_E OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
Source: "Microsoft SQL Server Native Client 11.0" Description: "Login timeout expired".
Source. "Microsoft SQL Server Native Client 11.0" Description: "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."
Source. "Microsoft SQL Server Native Client 11.0" Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".
One important thing to bear in mind is that both the source and destination databases are on this same server that the job is running from, meaning everything is localized and the domain service account is a local admin on the server and a sysadmin on SQL.
I have Named Pipes and TCP/IP protocols enabled on SQL. The service account running the job is a domain user that I have used hundreds of times on other servers setup for this same kind of work with never having a problem. I can connect via SSMS to this server from other VMs using the FQDN of the instance (i.e. SZDB.somewhere.com\SQL2014), and vice-versa.
So, open to suggestions here. There has to be something I am missing in the setup of my server.
We found that the solution in this case was to install a default instance of SQL Server. I previously only had a named instance running. As soon as I went through SQL setup and installed the default instance (i.e. MSSQLSERVER), the error on our ETL job went away and our data warehouse continued to build without any further issues. Proved to be the solution on two other servers as well that were exhibiting the same issue.
When i am trying to connect to the Azure DB from SQL Management studio an getting teh below error. Not sure why am getting this error as i was able to acess the DB erlier from SQL Management Studio.
Need help on this.
TITLE: Connect to Server
Cannot connect to ijk3ffy48i.database.windows.net.
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
BUTTONS:
OK
I think probably you haven't configure any Azure DB firewall rules to allow your computer's IP to communicate with your Azure DBs.
Simple things to check (not sure what you've tried so humour me here):
You're connected to the outside network.
Instance\Database name, username and password are correct.
Instance and database are online and connectable (Azure servers not down for scheduled maintenance or run out of paid services.)
Firewall rules are incorrect.
Also I think this question here is identical to your question. Try checking that out.
My goal is to connect to a Mongo database from Microsoft SQL Server Management Studio (SSMS) 2014 and be able to perform simple SQL queries.
I'm using Linked Servers connections through ODBC drivers.
I've tried the following drivers for Mongo:
Simba Mongo ODBC driver I stuck with error "Required conversion is not supported". But at least I was able to connect to Mongo server and see list of Mongo tables/collections.
Progress Mongo ODBC driver I stuck with error "Insufficient information to connect to the data source" (While test from ODBC Administrator is successful).
I would really appreciate any help about establishing connection between Mongo and SSMS.
Maybe you can recommend some specific ODBC driver for Mongo?