TMSPE error with External SQL DB

[Chris Swinney]

Hi All,

Someone posted a similar issue regarding TMSPE and an external DB although I'm seeing a slightly differnt error.

We have just upgraded from an old Windows 2003 machine hosting TMS (14.1.1) with TMSPE (1) and al local instance of SQL, to a new Windows 2008 R2 machine runing the same TMS (14.1.1) and TMSPE, pointing to a new SQL backend.

The main TMS DB seems OK, and even TMSPE connects fine to the SQL backend. However, when TMS shows a ticket say that TMSPE is not running (although the service has started - and has been set to auto start)  and when I browse the Provisiong section in TMS I get the follwoing popup errors:

Warning 
Unable to connect to the User Repository.
One or more unexpected errors occurred
Please see the console for details

I can't get to the configureation for TMSPE at all, and when I browse the diagnostics I see all red, wil a similar popup error as above:

One or more unexpected errors occurred
Please see the console for details

Has anyone got any ideas on what might be happening here?

Chris

[Magnus Ohm]

The reason for the error is most likely visible in the provisioning exstension logs and errors like this is mostly related to database connection issues. I would recommend openig a TAC case and upload the logfile to the case :)

/Magnus

Sent from Cisco Technical Support iPhone App

[Chris Swinney]

Thank Magnus. this is indeed what we did, although I resoled the issue before Cisco cam back with anything usefull.

It would appear that TMSPE takes umbrage to the database being moved after it has been installed and configured. So, I uninstalled TMSPE, restored the TMSPE DB from the old server to the new SQL backend, re-installed TMSPE, and low and behold it all started working – to a fashion.

Of course, all of the authentication principles are different in the new instance and the VCS’s could not authenticate with the TMSPE. However, this post resolved that issue as well, with Basic Authentication showing lower in the IIS global module list that Windows authentication. Moving Basic Authentication above Windows authentication resolved this issue.

It would appear the TMSPE is not quote as “mature” as the main TMS server application, and it doesnt take to kindly to being shaken around too much.

Many thanks

Chris

[Ali Khan]

Hi swinster70,

solution to problem is simple

1. Make sure remote database has SQL Browser service running

2. Open following ports on both Cisco TMSPE server as well as SQL server

a. SQL Server TCP 1433

b. SQL Browser UDP 1433

( You can type following script to do 2a, 2b, on both servers )

netsh advfirewall firewall add rule name="SQL Server TCP 1433" dir=in action=allow protocol=TCP localport=1433

netsh advfirewall firewall add rule name="SQL Browser UDP 1434" dir=in action=allow protocol=UDP localport=1434

Regards,

Ali Khan

[Chris Swinney]

Hi Ali,

Thanks for your reply, but I don't think you noticed that the problem was already resolved as per my previous post. It was not anything to do with ports or the browser service (this was all fine).

Unfortunately, you can make your own posts as "the answer". Often you either find the answer soon after posting, or this mere fact that you spend time to write down and think about the issue helps you resolve it.

Nice try anyway.

Chris