Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 days ago.
Improve this question
failed to initialize database, got error failed to connect to host=localhost user=postgres database=book: dial err
or (dial tcp 127.0.0.1:8080: connectex: No connection could be made because the target machine actively refused it.)
2023/02/12 18:12:18 failed to connect to host=localhost user=postgres database=book: dial error (dial tcp 127.0.0.1:8080: connectex: No
connection could be made because the target machine actively refused it.)
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 days ago.
Improve this question
I am getting an issue with the SMTP connection it keeps on saying Client not authenticated. I have set the SMTP Server to smtp.gmail.com and enabled the SSL layer socket. My connection string is below.
smtpServer=smtp.gmail.com;UseWindowsAuthentication=False;EnableSsl=True;
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 4 years ago.
Improve this question
Here the condition:
Let's say I have 2 SQL Server 2000 in my network :
sungai (192.168.1.63)
serverpc (192.168.1.200)
One of client PC can not connect to serverpc using "Computer Name" but works fine using IP Adress (ODBC and Query Analyzer), let say this PC as "Problem PC". 20 clients can connect to serverpc using Computer Name, just this "Problem PC" can't. "Problem PC" can connect to sungai using Computer Name and IP. I have checked nslookup and found no result using serverpc in my dns. This network using 2 router with 1 Subnet and Gateway.
I'm so sorry for asking. The problem is with Client PC.
Somehow there is sql server alias with name "serverpc" in this client PC.
I just remove it from "Client Network Utility" => "Alias" and works fine now.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
The server network address TCP://XXXX(Server Name):5023 can not be
reached or does not exist. Check the network address name and that the
ports for the local and remote endpoints are operational. (.Net
SqlClient Data Provider)
II am getting the above Error while doing mirror configuration.
Below are the steps I did for the Mirroring configuration.
Restored the fullback up to with no recovery option on secondary
server.
I tried restoring the Log backup (Error: RESTORE LOG is terminating
abnormally), hence I skipped the log restore.
I tired configuring the mirroring and got the success message for
mirroring configuration but when I start the mirroring my primary
database shows Primary/Synchronized where as my secondary server
shows in Recovery.
When I check the Sql ports in configuration manager it shows 1433 and
if I check tcp_endpoints it shows 5023.
Can you please help me to fix the Mirroring configuration.
I have tried Creating ENDPOINTS as-well and while creating PARTNER from Server A to B it is success but when i create partner from B to A it fails. I used below command:
ALTER DATABASE DBName
SET PARTNER ='TCP://XXX(Ip address):5023'
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I just installed PostGreSQL in my Ubuntu Box, and the first thing I want to do is to create a database. I read the documentation, and it simply says type createdb. Once I typed in that command, PostgreSQL gave me an error: could not connect to database postgres: FATAL: Ident authentication failed for user "myuser". I assume that this is because "myuser" does not have the right administration privileges in the database. Is there an easy way to add that priviliges ?
Thank you.
The postgresql usually creates a default user postgres. You would have entered a password during installation for this user. If you remember you can use it.
Otherwise, you can add an entry in the pg_hba.conf file to enable your localhost to login without any password for psql command.
A sample entry would be
host all all 127.0.0.1/32 trust
Perhaps, create a user first?
http://www.postgresql.org/docs/8.1/static/app-createuser.html
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I created a Terminal Services farm comprising of 3 TS hosts (say, TS1, TS2 and TS3) running Windows 2008 R2 Enterprise, a TS Connection broker and a TS Gateway for the purpose of hosting a windows application as a TS RemoteApp. The setup works just fine. Now, I want to do some further configuration changes on a particular TS host, say TS2 and not on any other TS host. I try to rdc to TS2 but I find myself getting connected to a randomly chosen TS host (sometimes TS1, sometimes TS2, and at other times, TS3). I think rdc connection is also going via the Connection Broker that is forwarding me to a TS host it decides is best. Is there a way I can deterministically connect to a particular TS host using rdc? I don't have option to login locally on a TS host as the entire setup is hosted in a remote data center. I think this is a very common scenario and must have a straight forward solution. It could be as easy as doing rdc to Connection Broker server and disabling it for a while, but I don't know how to do that too. Any help will be highly appreciated.
Figured it out...
One can use mstsc /console, or on more recent client versions use mstsc /admin to deterministically rdc to a particular member of a load balanced TS Farm.