themarsvoltaire Posted March 23, 2014 Report Share Posted March 23, 2014 I just setup an vm instance of Windows Server 2012 Datacenter with SQL Server 2012 in Azure, but the service is having trouble connecting to SQL Server when I changed the backend. I've attached my db.conf and the log file that is created when I try to start the service, please ignore the *.txt extension. I tried adding "NT AUTHORITY\LOCAL SERVICE" to SQL Server logins via management studio. db.conf.txt plastic.server.log.txt Link to comment Share on other sites More sharing options...
manu Posted March 24, 2014 Report Share Posted March 24, 2014 Hi! the following error: ERROR Codice.CM.Server.RepositoryHandler - Login failed for user 'WORKGROUP\EGSCM$' Makes me think of a bad password or a bad user name. The dollar char at the end smells bad, can you please try with an easier name just in case? Link to comment Share on other sites More sharing options...
themarsvoltaire Posted March 25, 2014 Author Report Share Posted March 25, 2014 I'm not actually sure where the $ came from. The administrator account name is just "egscm". Link to comment Share on other sites More sharing options...
manu Posted March 25, 2014 Report Share Posted March 25, 2014 For some reason SQLServer is having a request from 'WORKGROUP\EGSCM', can you check the user you are using at the "db.conf" file? If you are using the Windows based authentication you can try to switch to the SqlServer user/password mode and check if makes a difference. Remember that this mode is not enabled by default so you will need to activate it inside the SqlServer management tool. You can check this guide: http://www.plasticscm.com/infocenter/technical-articles/kb-how-to-configure-plastic-scm-with-sql-server.aspx Link to comment Share on other sites More sharing options...
themarsvoltaire Posted March 25, 2014 Author Report Share Posted March 25, 2014 That didn't seem to have any effect. The resulting server log is identical. If it helps, I just learned that the $ at the end of the account name means that it is a Managed Service Account. EDIT: Or it possibly means the account is in Active Directory... Link to comment Share on other sites More sharing options...
manu Posted April 1, 2014 Report Share Posted April 1, 2014 The original message makes me think the issue is at the SQLServer side Login failed for user 'WORKGROUP\EGSCM$' Did you try login into the SQLServer management tool with that user accont? Does it work? Can you try to switch to SQLServer user/password mode and try if it works with a valid user? Link to comment Share on other sites More sharing options...
themarsvoltaire Posted April 8, 2014 Author Report Share Posted April 8, 2014 I ended up deleting and re-creating the VM instance, and this time it worked perfectly (using the hostname for SERVER in the connection string, which I had tried before). Not sure what it was, but thanks anyway. Link to comment Share on other sites More sharing options...
manu Posted April 11, 2014 Report Share Posted April 11, 2014 Wow! Well, at least you have it working.... Not sure what was happening..... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.