cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1864
Views
0
Helpful
18
Replies

TMSPE with external SQL issue

Mattias Widman
Level 1
Level 1

Hi all,

thought I´d give the forum a try trying to solve an issue I´m seeing at a client site. We are trying to migrate from TMS Agent Legacy to TMSPE and we´re a bit stuck.

During installation I get an error stating that it is "Unable to establish SQL connection through JAVA runtime. Check your SQL Protocol settings".

The SQL database tmspe has been created on en external SQL server in the same instance as the tmsng database located at

vgdb0297.domain.se\i01,63335 . The account we are using has dbo rights to the database.

The SQL server doesn´t have SQL Server Browser running which is why we are pointing to the instance.

I have double checked the credentials, configured the windows firewall to allow all traffic out to that port (doesn´t help if I allow all ).

Screenshot_2013-03-06_14_13.png

Any ideas on how to solve this? Enabling SQL Server Browser on the SQL is not an option

//Mattias

18 Replies 18

@Justin:

Doesn´t work either

Anyway, I guess I´ll have to try and force the client to setup a separate server for this or use a local SQL Express

//MW

Justin Ferello
Level 5
Level 5

Mattias,

Can you show us your TMSNG connection information from the TMS Tools application?

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
e/v: justin.ferello@kbz.com

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

Unfortunately not at the moment, not on location and no VPN

But this was the search string I entered while installing the TMS vgdb0297.domain.se\i01,63335 and enter the username for the dbo account. On that location we had restored a backup of the tmsng database from their old server. It found it right away and after install reboot everything was back up & running and all I had to do was redirect the A-record. Worked like a charm

For security reasons I´m not allowed to print out the domain.

So it seems that it should work according to the guide page 71 to enter 101:63335 as the instance but no luck so far.

//MW

We have a similar issue with TMSPE having just switched from a standalone TMS/SQL setup to a new TMS fornt end and separate SQL machine, so I'm interested in the outcome of the thread. Our issue is slightly different in that it looks as though TMSPE connect fine to the DB, but it still throws a random error. As it slightly differnt, I am goin g to start a new thread.

Chris