I've been trying to figure out this issue for hours now.
I have 3 stations on the same network, all in which can talk to each other (I have folders shared on each computer that the others can access). The main station where the database is being held works with no problem. I can wrong the program and it can access the database, I can make changes etc.
Now when I attempt to connect the other stations to the master, I get an error:
Provider: Named pipes Provider, error. 5 - Invalid Parameter(s) found.
The following things are what I have done:
disabled firewall
shared SQL folder along with giving "everyone" full control
"everyone" has full access to the Data and Log folder
enabled the shared memory, named and TCP/IP pipes in Server Config Manager
I have a password for SA and I am using it to connect to the DB
DBConfigurator can connect to the DB from Station 2 (child) to Station 1 (master) with no issues but fails and ask for database settings when I open the program
Sorry if this is a little confusing but I don't know where else to go.
Related
I have Microsoft SQL Server 2016. I used to go in with a server name and there was no problem.
Recently there was a problem with the boot file, also known as the 0x00000034 blue screen error.
After the patch, it does not let enter the local server name.
Before
but the result
I tried other names and also examined similar questions without any good results.
for example-
How to find server name of SQL Server Management Studio and also How to find server name of SQL Server Management Studio but without any success.
There might be an issue with the connection to the server instance. I would try the troubleshooting steps in the question and answer from this post How do I fix the error 'Named Pipes Provider, error 40 - Could not open a connection to' SQL Server'? or from this video https://www.youtube.com/watch?v=810cv3PunkA
The server name, that you enter there is the name of the computer, on which the SQL Server has been installed. This is called "default instance", because you do not specify a name of the instance, which is in the format "computer_name\instance_name". If you are trying to connect to an instance (either default or named) installed on your local computer, you can substitute computer_name with . (dot), i.e. you can connect to a default instance on your computer by giving ., or to a named instance as .\SQLEXPRESS for example.
So in your case if you specify only a dot for server name, you should be able to connect. If you don't connect, then the SQL Server instance is not working. You can check is the service started, but you may have to reinstall SQL Server.
If the connection is successful, then you can keep using . (or (local)). If you want to find your computer's name, from Windows Explorer right click This PC and select Properties, then look at Computer name:.
If you still can't connect to the SQL Server using this computer name, then you have issues not related to the SQL Server engine itself. Open a command prompt and try to ping the computer name: ping desktop-7t2s4sm. If you get an error, then you have a networking issue.
Press ⊞ Win + R or type run in start (open run)
Type services.msc
Look for SQL Server (MSSQLSERVER)
Right click on it
Click on start
Is it possible to create public database link to SQL Server using Windows Authentication from an Oracle DB?
I can create the link
CREATE PUBLIC DATABASE LINK DB_LINK CONNECT TO "domain\user" IDENTIFIED BY "password" USING 'tns_name_entry';
But when I try a select statement
Select * from dual#DB_LINK
I get the following:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from DB_LINK
28545. 0000 - "error diagnosed by Net8 when connecting to an agent"
*Cause: An attempt to call an external procedure or to issue SQL
to a non-Oracle system on a Heterogeneous Services database link
failed at connection initialization. The error diagnosed
by Net8 NCR software is reported separately.
*Action: Refer to the Net8 NCRO error message. If this isn't clear,
check connection administrative setup in tnsnames.ora
and listener.ora for the service associated with the
Heterogeneous Services database link being used, or with
'extproc_connection_data' for an external procedure call.
Error at Line: 9 Column: 20
I can connect to the db, so it's not an issue of connection. The heterogeneous service has been created, and the listener.ora and tnsnames.ora have been edited. I'm wondering if I'm getting the error because I'm using Windows authentication. Thanks.
Figured out my problem. It has something to do with Oracle12. You have to start the listener as the local account. Go into services --> right click properties of the listener --> Log On. Also you don't need the domain when creating the database link.
Ok, one physical server running Hyper-V. One VM is for the SQL 2016 DB. Another VM is for the web based application that talks to the DB. A third VM that is used as the file server. All files are stored on the file server.
The file location that needs to be bulk inserted is shared with the DB Service Accounts (currently set to specifically made domain accounts - one for each service).
The file can't be imported - access is denied. I've tried setting the share to Everyone - still doesn't work. I even changed the Security Policy to allow Anonymous users the same permissions as Everyone - still doesn't work.
I don't know how to go about this Delegation method so not sure what to do there.
What else can I do to get a simple file to import into a DB?
Have you enabled kerberos? If the connection is coming in as Anonymous, dosent it mean that the connection is using NTLM and its a double hop issue?
I am currently trying to take backup of a database to a network UNC share, but its giving me error.
I have two PCs connected in a simple NETWORK, not a domain.
From both pcs, I can easily create and edit files on either one.
One PC on which SQL SERVER is running and database files are located, is named SERVER.
Another PC on which I want to take backup, is named STUDENT-PC2. On this pc, drive d: is a shared drive and I set the full permission for this folder for Everyone, IUSER,NETWORK,NETWORK SERVICE
When I run following command from SQL SERVER MANAGEMENT STUDIO on SERVER, it throws me error as below.
I am running sql server service as NETWORK SERVICE
COMMAND
backup database dpmt to disk='\\STUDENT-PC2\d\DPMT_BACKUP_17032016_102719.Bak'
ERROR
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device '\\STUDENT-PC2\d\DPMT_BACKUP_17032016_102719.Bak'. Operating system error 5(Access is denied.).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
On computer "STUDENT-PC2" locate the file share that is destination for backups. In file share permissions add account named as your SQL machine plus dollar sign, like this: "SERVER$" - type that instead of username. Tick write+read permissions for that artificial "user", and hit OK to close. On the file system level configure permissions the same (write+read) or let Everyone write at first to test and then reduce.
In summary:
if both computers are not part of the same domain, the other computer (STUDENT-PC2) sees all local accounts from "SERVER" as "SERVER$" account, no matter what they real name is.
you need to set permissions on destination (STUDENT-PC2) for account "SERVER$" at two levels: file share permission level, and ntfs file system permission level.
I have this problem which I am trying to debug for a lot of time.
The setup is like this:
i. The application is a Windows application developed using VS2005, .net 2.0.
ii. I use the Cyrstal reports component Crystal Report Viewer and dynamically display various reports in the same form.
iii. The db is SQLSERVER Express 2005 and situated on a different machine.
When I run the application on the db server, I am able to view the report. However, when I run the application on a different machine which is connected to the above dbServer, I get an error. ( I dont get this error on my dev setup)
Source: CrystakReprotViewer.CS:SendDBLogonForReport() Details:Logon failed.
Details: ADO Error Code: 0x
Source: Microsoft OLE DB Provider for SQL Server
Description: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection.
SQL State: 08001
Native Error:
Error in File C:\DOCUME~1\admin\LOCALS~1\Temp\ActionPoints {52820D22-199C-4D46-A76B-70A55D9F54D5}.rpt:
Unable to connect: incorrect log on parameters. at CrystalDecisions.ReportAppServer.Controllers.DatabaseControllerClass.SetTableLocation(ISCRTable CurTable, ISCRTable NewTable)
at CrystalDecisions.CrystalReports.Engine.Table.set_Location(String value)
at Trivalve.UI.Client.Reports.CrystalViewer.CrystalReportViewer.SetDBLogonForReport(ConnectionInfo connectionInfo, ReportDocument reportDocument) in D:\Ramjee\Work\Projects\Trivalve\Trivalve\src\tfssetup\2008\Trivalve_2008\Trivalve\Reports\CrystalViewer\CrystalReportViewer.cs:line 127 rptcontrollers.dll SetTableLocation
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks,
Ramjee
Use datasource=servername or ip address\instance name if available,port number
Default port number is 1433 or 1434
My problem was solved with this. Posting for the use of others.
If this is a standard installation of SQL Server Express, bear in mind that the only connection method installed by default is shared memory, and is only available on the server -- you would need to enable another connection protocol such as Named pipes or TCP/IP. To turn networking on, Use SQL Server Configuration Manager to enable relevant protocols and start SQL Browser.
It's telling you exactly what's wrong.
Details:Logon failed.
Great, we can't logon.
(Invalid Instance()).]Invalid
connection.
Okay. I bet we have "localhost" as part of the instance name in my connection string. Since I'm no longer on the "localhost", this obviously won't work. Let's try there first. Then perhaps it's the credentials that I'm using to query my database. Usually what I do is create a RO user that can only do selects on my db and use that for CR. If none of these are getting me close, let's try making sure that remote connections are enabled for SQLEXPRESS
Unable to connect: incorrect log on
parameters.
Ok it's definitely a connection issue.