Error while creating a server

[lucarossini]

Hi,

Today I was trying to set up a server following this -> tutorial.
Everything went fine till the end, exept for the fact that whenever I start the server, every service is stuck in pause (starts for a few seconds but quickly pauses again).

I did everything according to the guide, the server should be lan so everything is on 127.0.0.1

Looking in many threads I just found "check ini files for mistakes in user/password .." but rest assured they are correct, I checked so many times that I'm about to learn the encrypted password by memory.

Here are the logs that appear each time I start the services:

From ShaiyaServer\PSM_Client\Bin\Log

 Spoiler

2014-07-16 03:27:52 PS_USERLOG__system log start (UserLog)

2014-07-16 03:28:09 DB userlog connect error, Server=127.0.0.1, DBName=PS_UserData, User=Shaiya, Pass=Shaiya123

2014-07-16 03:28:09 3 1 SService::ServiceCtrlDispatcher(): m_pService->Init()

2014-07-16 03:28:09 PS_USERLOG__system log end (UserLog)

2014-07-16 03:28:09 3 1 SService::ServiceCtrlDispatcher(): service shutdown

Additional info : I created the user in SQL Server Management with all the correct permissions, the .ini files ARE CORRECT and match with the password
I enter in the main panel of the server (of course in the .ini it is encrypted).
I made 2 more users with 2 different passwords, always stuck at the same point.

[Boul27]

It's a probleme withyour SQL account

Be sure that the encrypted password in your .ini is correct
try to connecte in SQL Server Management with a sql account (like Shaiya/Shaiya123 ) to check the permissions n this account (don't use the windows authentification)


I'm not a pro, but maybe it can help you

[lucarossini]

The .ini files are correct. I can connect manually with SQL management using the user data that I wrote in the server config. The account has maximum DB permissions..

[Boul27]

Hum, if you can connect with your account, it's very strange

wait for better help than mine

Sorry, and good luck

[lucarossini]

To anyone having this issue, after hours of searching I finally found a solution, just needed to use a different version of SQL Server (R2 Service Pack 2) and same for Management.

The topic can be closed.