October 26, 2018 at 2:40 am
Hello,
Not sure where to post this, but this is bugging me for a while.
Since Oct 5th I cannot connect anymore to my SQLserver 2012 with SQL studio, and also the SQLAgent jobs are failing on the server, without any message than its connection is established but closed.
I have restarted the services, no luck
reset all possible connection methods (names pipes, shared memory, TCP/IP no luck.
Using SQLCMD to connect to the sql server works fine, so at least I can access the ssqlserver.
And using an sqlstudio from another server in the same network, all is fine to connect ??
The issue is within the SQL server itself I guess,. And if my backups were running fine via the SQL agent, I was not too worried, but the agent does not work as it accesses the jobs from the server itself and give again the nice errors.
The SQLserver logs are not displaying any info, only when I stop and start the services it does mention info, but nothing more.
Also I looked into the amount of accounts for logon, which is correct, it is a mixed authentication, so all looks fine, and normal.
and as mentioned I can logon with SQL studio from other servers.
A reinstall of SQL studio does not see a solution, because I can use the sqlstudio on this server (with the werid issue) to connect to others server.
So yeah, a bit weird. but hopefully somebody knows a possible solution or find a hint how I can continue, without a complete reinstall 🙂
December 18, 2018 at 11:50 pm
SQL Error 233 causes while accessing the database, sometimes user faces the situation when they log in into SQL Server Authentication mode, and it display error message 233. This may help you out:
https://www.sqlserverlogexplorer.com/fix-login-failed-error-233/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply