Unable to Connect to New Server

[mattgoff]

I've trawled the archives and see some references to this issue, but none with a concrete resolution. I'm getting ready to rebuild my database from scratch (we're completely changing our chart of accounts, kill me now). I started on my dev server by spinning down the instance and deleting all of the database and log files. I restarted the instance and it recreated the base files normally. I can connect locally using the default credentials.

The problem: I cannot connect remotely.

• If I use the local admin server, a remote Perspectives client can't see the server at all.
• If I use my production admin server, I can see the server but if I double-click it I get an hourglass for a few seconds. Then it returns to the regular pointer with no open server.
• If add IPAddress=T or IPAddress=[theActualAddress] to the cfg file, I can get to a login prompt but the following error after I press OK: "Specified server not found."

I have a PMR open w/ IBM but as a Sev3 they're not rushing to help. And since it's a dev server I can't really justify a higher severity.

Other things I have done:

• Uninstall (and delete all registry keys) and reinstall TM1 with 10.2.2 FP6 and redo the manual SSL certificate server-side edits to use v2.
• Delete and re-register the SSL certificates per a Technote.
• Disable all network connections except the single one in use, disable IPv6, confirm only one IP address is assigned via ipconfig.
• Confirm that Windows Firewall is disabled on both machines.
• Confirm that virus/malware scanner did not block connect attempts to any TM1 ports.
• Confirm that no other TM1 servers are running on this server to complete for ports.

At this point, I'm out of ideas. If anyone has run into this before or has a suggestion I'd appreciate hearing them.

Matt

[mattgoff]

IBM got back to me, and the problem is solved via a Technote. Since the server is FP6 but my client is pre-FP6 I needed to make a couple config changes. The server cfg needed to have SupportPreTLSv12Clients=T added. There's a similar flag in Cognos Configurator under TM1 Admin Server. Posting here for the next person who, like me, lets client versions lag server. IMHO the default should be the opposite-- let people who want to lock down security set it to false.

Matt