TMS 14.1 Upgrade Error

[Justin Ferello]

Hey all,

I was running TMS 14.1 Beta (Yes I am part of the EFT) with PE and everything was running fine.  I decided to upgrade to TMS v14.1 final today and now TMS will not talk to PE anymore.

I am seeing the following error over and over again in the log-tmsagentproxy.txt file:

2012-12-19 10:13:41,397 [7] WARN  Tandberg.TMS.Framework.Proxy.ReverseProxy - Request failure: http://localhost:8788/dr/groups/id/b8e3d61c-8567-477b-921b-2cbbe8c181a3

2012-12-19 10:13:41,397 [7] ERROR Tandberg.TMS.Framework.Proxy.ReverseProxy -

System.Net.WebException: The remote server returned an error: (503) Server Unavailable.

   at System.Net.HttpWebRequest.GetResponse()

   at Tandberg.TMS.Framework.Proxy.ReverseProxy.ProcessRequest(HttpContext httpContext, Dictionary`2 proxyRequestHeaders)

The TMSAgent service is running & so is the TMSPE service.  Please help

Thanks,

Justin

[Justin Ferello]

Guys,

I installed said hotfix, rebooted and still having the same issue.

Seems like PE is not wanting to move to TCP, still stuck on PIPEs.  I am free for a WebEx if anyone is interested

2012-12-19 18:28:06,474 [dg] [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] WARN  U: c.m.v.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@99e8f8 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (5). Last acquisition attempt exception:

java.sql.SQLException: Network error IOException: \\TMS\pipe\MSSQL$SQLTMS\sql\query (Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator)

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.(ConnectionJDBC2.java:395) ~[jtds-1.2.4.jar:1.2.4]

at net.sourceforge.jtds.jdbc.ConnectionJDBC3.(ConnectionJDBC3.java:50) ~[jtds-1.2.4.jar:1.2.4]

at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184) ~[jtds-1.2.4.jar:1.2.4]

at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) ~[c3p0-0.9.1.2.jar:0.9.1.2]

at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) [c3p0-0.9.1.2.jar:0.9.1.2]

Caused by: java.io.FileNotFoundException: \\TMS\pipe\MSSQL$SQLTMS\sql\query (Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator)

at java.io.RandomAccessFile.open(Native Method) ~[na:1.6.0_33]

at java.io.RandomAccessFile.(Unknown Source) ~[na:1.6.0_33]

at java.io.RandomAccessFile.(Unknown Source) ~[na:1.6.0_33]

at net.sourceforge.jtds.jdbc.SharedLocalNamedPipe.(SharedLocalNamedPipe.java:61) ~[jtds-1.2.4.jar:1.2.4]

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createNamedPipe(ConnectionJDBC2.java:503) ~[jtds-1.2.4.jar:1.2.4]

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.(ConnectionJDBC2.java:320) ~[jtds-1.2.4.jar:1.2.4]

... 10 common frames omitted

[daleritc · Accepted solution]

Just disable Named Pipes so has to force TCP and I'm also begining to think about the mssql properties file for TMSPE since you mentioned trying to use the TMS Tools...meaning I wonder if the properties file is incorrect in some way. However, the quick and dirty here would be to uninstall and reinstall TMSPE.

As far as webex, getting way to late for me and already on a very long day now so I actually gotta get home else I won't have a home...if you catch my drift

[Magnus Ohm]

Justin

You disabled the pipes right in SQL config and set TCP IP priority to 1 etc?

This should have resolved your issue. Try to re-install the application, the data is still in the exsisting tmspe database If that does not do the trick, open a TAC case. I am on xmas vacation so I can´t do a webex atm. 

/Magnus

[Justin Ferello]

Guys,

Thank you so much for the help.  I just did an uninstalle/re-install of PE, it seems to have resolved the problem.  Would like to know more about the 'SQL config file' you mentioned Dale.  If I run into this type of issue with a client it looks much better if I can edit a file and fix the problem than say the typical 'uninstall/re-install should fix it'.

I noticed after the re-install the PE service is set to manual, should this be auto or manual?

Thanks,

Justin

[daleritc]

Hi Justin,

Not sure that was the 'crux' of the problem, it was probably more the 'lock' on named pipes being enabled...which is more of curiousity to me and I'm hoping is just a coincidence...which I believe it is since we haven't come across any similar issues like this and we have been doing uprades/installs of both TMS 14.1 and TMSPE on TMS Appliances.

As far as the PE service, the following is from the 14.1 release notes:

For new installations of Cisco TMSPE with Cisco TMS 14.1, the TMS Provisioning Extension Windows service will have its Startup Type set to Manual. To automatically start Cisco TMSPE after server reboots, change the Startup Type to Automatic using the Windows services panel.

This will be fixed a later release of TMSPE, i.e. coming in April - May this year.

Glad to hear you got things going. I can now go to sleep

cheers,

Dale