Error When Trying To Connect Remotely Follow

0
Avatar
Legacy Poster

Using the Enterprise automation edition whenever I attempt to connect a desktop to a BarTender database that is located on a server I get error #1047 "A Connection to SQL Server SERVER\BARTENDER could not be made. I have subsequently from the same desktop connected to the database using SQL management studio so I am only having this issue from within BarTender. Anyone run into this? I don't recognize the error message.

8 comments

0
Avatar
Shotaro Ito
Moderator
Comment actions Permalink

Hi,
Do I understand that you're trying to connect BarTender System Database(for database logging)?
That access was done by "BarTender System Service" service, which needed to be logon by an account which has access rights to the SQL server.
(Local System Account doesn't have network access rights.)
You can specify account at BarTender installation or Windows Management console > Service and application > Services > [BarTender System Service]'s logon tab.
You can connect with Windows authentication or SQL authentication(username and password). for detail, please check
BarTender Help > Companion applications > System Database Setup > Remote Connection.
Hope that helps.
0
Avatar
Legacy Poster
Comment actions Permalink

Hi Shotaro,
The BarTender System service is running under a account that was created specifically for this purpose. It does have the proper access to the SQL Server database but still we cannot connect remotely from BarTender on a remote client. Note that the BarTender app running on the same server can connect to the database no problem. Do you have any information on Error #1047?

Regards
0
Avatar
Shotaro Ito
Moderator
Comment actions Permalink

Don't have a clear thought - though you need to figure out whether that is permission issue or network issue.

Could you connect to the SQL server by SQL Management studio on Client, with SQL authentication?
[url="http://msdn.microsoft.com/en-us/library/ms144284.aspx"]Choosing an Authentication Mode[/url]

Or If you can connect the SQL server by via SQL Management studio with Windows authentication (that means you login SQL server by your Windows login account), what happens when you enter your login account to BarTender System Service's logon account?

Try connect from BarTender History Explorer to the remote system database too.
0
Avatar
Legacy Poster
Comment actions Permalink

Ok, looks like we were able to resolve it, the problem was the client workstation used the user ID of the person that installed the software on the BarTender service, when we changed the userid that the service uses to the account that was used at the server it worked. We still can't seem to figure out why this is as the accounts have the same rights etc. Is there any white paper that explains what goes in the two groups that are created on the server? One is called "BarTender users" the other is called "SQLSERVER2005MSSQLUSserXXXXXX$BARTNDER"
Thanks in advance.
0
Avatar
Shotaro Ito
Moderator
Comment actions Permalink

[quote name='AdvancedSolutions' timestamp='1329421730' post='1753']
Ok, looks like we were able to resolve it, the problem was the client workstation used the user ID of the person that installed the software on the BarTender service, when we changed the userid that the service uses to the account that was used at the server it worked. We still can't seem to figure out why this is as the accounts have the same rights etc. Is there any white paper that explains what goes in the two groups that are created on the server? One is called "BarTender users" the other is called "SQLSERVER2005MSSQLUSserXXXXXX$BARTNDER"
Thanks in advance.
[/quote]
Hi - Sorry for took long time, got answers about it.
The BarTender Users group is created during install and is used for BarTender System Service and Commander if the user elects to add credentials on the user account page of the installer. The group is also used by the BarTender Web Print Server user account for automation calls to BarTender.

The other one "SQLSERVER2005MSSQLUSser$<computer name>$<instance name>" is created by MS SQL Server installer and required for SQL Server.
[url="http://msdn.microsoft.com/en-us/library/ms143504(v=sql.90).aspx#Review_NT_rights"]MSDN: Setting Up Windows Service Accounts[/url]
0
Avatar
Legacy Poster
Comment actions Permalink

Thanks both of you, I was going through this exact same issue and your post, AdvancedSolutions, fixed this.

 

Thanks!

0
Avatar
Legacy Poster
Comment actions Permalink

Hi.

 

I know this topic is a little bit old, but I'm experiencing the same error. I think I've tried everything in order to fix it, but nothing works. Some of those things are:

 

  • I've installed SQL Server instance named BarTender with the BarTender default database thru System Database Wizard in a test server that is within the company's domain (lets call it...companydomain).
  • I've granted full access to the BarTender SQL Database to an user (lets call it...testUser) which is in the company's domain.
  • In the testUser's computer (who has BarTender 9.4 suit installed), I've started the BarTender System Service logged on with the companydomain\testUser account, and I've restarted the service.
  • When I try to configure the database connection in the System Database Wizard, I pick the SQL server instance from the list (the icon shows the server as online) and I choose Windows Authentication mode (I am logged in the computer with the companydomain\testUser account), the error of this topic shows up. The curious thing here is that if I connect within the same windows session to the BarTender Database using the SQL Server Management Studio, it works! I'm able to do select, insert, update and delete operations.
  • I've also created a SQL Server user named bartender and associated it to the BarTender Database. When I try to connect from the System Database Wizard, I choose SQL Server authentication in the Wizard, type the bartender username and password and the exact same error appears. If I try to connect to the BarTender Database with the bartender username and password, it works!

Please help! What can I've been doing wrong?

 

Thanks!

0
Avatar
Shotaro Ito
Moderator
Comment actions Permalink

Mmm. Try re-create system database from wizard.

In SQL sever, grant full access (sysadmin) to the test account.

In Windows Service, set BarTender system service's logon account as the test account. Restart bartender system service.

In System DB Setup wizard, connect to the SQL Server and create a new system database (bartender2 etc).

Please sign in to leave a comment.