I recently upgraded to Maximizer 12. It has not gone very well up to this point.
My current problem is as follows. Every few days a random workstation refuses to connect to the SQL server. Maximizer will not load at all, the MAXAPP.EXE process cannot be ended and you have to wait several minutes for it to time out and give up.
Now, here is where it gets weird. I can create an ODBC connection with named pipes or TCP/IP, I can remote desktop to the server from the client, I can ping the server by hostname and IP address and I can map a network drive. Even Maximizer can see the server, but just not the SQL instance.
The only clue I have been able to dig up is that when I create an ODBC connection I have to specify the TCP/IP port, if I leave it checked as dynamically find port then it times out.
Also, when the Maximizer starts acting up, sometimes drives I have mapped fromt he client to the workstaion will disconnect and time out, but they will work from other workstations.
Here are the server workstation specs
SERVER:
Currently is functioning as only 2 things, a file server and Maximizer 12 group for 8 clients.
8 3 ghz cores
32GB of Ram
win 2088R2
CLIENT WORKSTATIONS:
All but one are running Windows 7
the one is running Windows XP
I have had the issue on almost all of them
Original Post