I already downloaded the oracle developer tools for VS, then I tried connecting HR to Visual studio with this configuration:
my configuration
but gives me this error:
ORA-12514, TNS:listener does not currently know of service requested in
connect descriptor
how do i resolve it?
Your configuration specifies to request a connection to service 'orcl'. But the error message says the database listener (the process responsible for handling the connection request) does not know of any database services 'orcl'. To fully debug, we'd need to see the output of the command 'lsnrctl status', as executed on the database server machine. Most like cause is that the database itself is not started, and thus is not registered to the listener.
Related
I'm trying to connect to an SQL database hosted on Azure from a function app I'm building in Visual Studio but I'm getting the following error:
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 - An attempt was made to access a socket in a way
forbidden by its access permissions.)
I can connect from the same PC using SSMS without a problem. I've tried connecting to the database using data connections in server explorer in VS but I'm getting the same error. If I connect to Azure with my account in server explorer it shows me a selection of services including SQL databases but there are none listed underneath although my account does have access to the database.
Are there any hidden gotchas I'm missing or settings within VS? I've also tried adding my client IP in the firewall settings but that didn't make a difference either.
After doing some more testing it turned out to be the client firewall that was blocking VS and VS Code from connecting to Azure SQL. It seems there was already an exception for SSMS.
The error message states "Verify that the instance name is correct"
It could be that the SSMS is automatically creating a fully qualified name once you say that it is an azure database.
If you use the short name from Visual Studio, then you cannot connect to the SQL server.
For example "myserver.database.windows.net" versus "myserver".
I am having an issue connecting to an Oracle database when running an SSIS package in debugging mode in Visual Studio. I am using Visual Studio 2012 with Data Tools installed and an Oracle 10g client.
I am using the Oracle Provider for OLE DB that came with the 10g client. I can create a Connection Manager connection to the server and test connectivity fine. I can also preview the data from my query in the OLE DB Source editor. It only fails to connect during debugging.
The actual error message is:
Error: 0xC0202009 at TW_Billing, Connection manager "server.schema": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-12154: TNS:could not resolve the connect identifier specified".
Error: 0xC020801C at Data Flow Task, ERDB Billing45 Source [2]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "server.schema" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: ERDB Billing45 Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
Most of the research I have done on this issue points to a 32bit error. I tried setting the ForcedExecutionMode to Int32 and ForceExecutionMode to True. I also changed the project properties to Run64bitRuntime to False. Neither of these made a difference.
If it makes a difference, we are using LDAP for Oracle connections. That said, I usually dont have an issue connecting to the TNS Names server (I.E. I can connect to the Oracle server any which way other than in Visual Studio debugging mode).
So I apparently failed to install Oracle Developer Tools for Visual Studio:
http://www.oracle.com/technetwork/developer-tools/visual-studio/overview/index-097110.html
Installing this in a new Oracle Home location and re-starting Visual Studio solved my issue. Packages now run during debugging correctly.
I'm trying to setup reporting in TFS 2010.
I can't connect to the Analysis Services database and I also can't rebuild the Analysis services database.
I've tried to connect via TFS Admin console and SSMS and I'm getting this error in SSMS
Connect to Server
Cannot connect to xxx.com,1031.
ADDITIONAL INFORMATION:
A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)
The requested name is valid, but no data of the requested type was found (System)
and this error in TFS Admin
The SQL Server instance that you specified was not found or cannot be reached. Specify another server or instance.
The sql server analysis services service is running.
I used the following article to identify the correct port for SSAS service and I still cannot connect.
http://support.microsoft.com/kb/2466860
Any ideas would be appreciated.
It was the port number.
I fixed it by using the above link to identify the port number then connecting using TFS Admin tool.
When in try to start azure storage emulator i get the following error.
Probing Failed. Retrying probe for localDB
Probing SQL Instance: '(localdb)\v11.0'.
Caught exception while probing for SQL endpoint. 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: SQL Network Interfaces, error: 50 - LocalDB error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
)
Number of SqlErrors Reported: 1
SqlError: System.Data.SqlClient.SqlError: 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: SQL Network Interfaces, error: 50 - LocalDB error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
)
LocalDB is installed but is not functioning properly. You may be missing prerequisites. Make sure you have .NET 4.0.2 or higher installed.
No SQL Instance found.
One or more initialization actions have failed. Resolve these errors before attempting to run the storage emulator again. Please refer to go.microsoft.com/fwlink/?LinkID=248088 for more details.
I installed .net 4.0.2 also. I tried uninstalling and installing sqllocaldb as well.
Any help is highly appreciated.
I had the same problem.
After installing .NET framework 4.5, the problem is gone for me.
I was also facing same kind of problem when reinitializing Storage Emulator. I used "Autodetect" parameter at command prompt and it worked for me.
DSInit /sqlinstance:(localdb)\v11.0 /Autodetect /ForceCreate
Hope this help to you too.
Amit
It would be better if you can check again if local DB is correctly installed and started. Please refer to SQL Server 2012 Express LocalDB for more information.
been trying to configure an ADO.NET connection for my Visual Studio application but I am running into issues and having no luck at all troubleshooting them. The major error that I run into is:
A network-related or instance-specific error occurred while establishing a connection to SQL server. The server was not found or not accessible. Verify the instance name is correct and that SQL server is configured to allow remote connections (Error 40: Could not open connection to the SQL server)
The steps I undertook to troubleshoot this are:
1. Open up Sql server configuration manager and under the SQL Server Network Configuration, Protocols for MSSQLSERVER,SQLExpress, SQL server 2008 connection string data source I enable each of the protocol names (Shared memory, Named pipes,TCP/IP,VIA)
As instructed I stop the SQL server services first under the SQL server services nodes.
Now I click start, MSSQL server service starts but both SQL Server 2008 and SQLEXPRESS agents do not. Stating the following:
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 might just be the problem as when I attempt to create the connection string , the server name specified is MYWORLD/SQL SERVER 2008. Since the SQL server 2008 agent service refuses to start, the connection fails, leading to the first error message.
Does anybody have any leads on this and can let me know the necessary steps to mitigate this.
The SQL Browser service must be running to connect to a named instance.
Use SQL Servr Configuration Manager under Configuration Tools under Microsot SQL Server 2008 to assign the logon accounts for each service you want to run. Do NOT use any other method to assign user accounts because the correct rights will not be enabled.