Wednesday, March 11, 2015

Cisco IM&P External Database Username Password

Client experiencing several issues with IM&P, one of which is an error found on Diagnostics | System Troubleshooter.  The External Database Troubleshooter tests indicated the external database was pingable, but the connection was failing.  The External Database Settings indicated the solution was "Verify the hostname, username, and password are valid."

The usernames and passwords were reset, the external database re-associated, the message archiver settings reset, XCP Router restarted,  etc., etc.  The PostgresSQL user was made a superuser, connections could be made manually, the PostgresSQL config files and schema was thoroughly checked and it was discovered instant messages were logged appropriately, even with this error. My predecessor must have been satisfied things were therefore fine, despite the error messages. I can't personally can't stand things almost being finished.

The fix? The fix was ultimately simply changing the DB user password to something that did not include the '$' character.

Hours wasted.

Hope it helps.

Wednesday, March 04, 2015

IPCelerate IPSession database cleanup procedures

This is likely dated material as I haven't had the chance to work with IPCelerate based solutions in years, but the following just helped me out of a jam.  The issue was communication between a Status Solutions TAP paging interface, the IPCelerate IPSession server and ultimately Cisco 7925 handsets was delayed.

1. Open up Windows Service and stop the following services:
   Apache Tomcat Tomcat5

2. Open command prompt and type osql -E

3. Then type the following commands
   1> use nipa
   2> backup log NIPA TO DISK ='NUL'
   3> go

Note: This may take a few minutes before you receive a message similar to this:
      Processed 33136 pages for database 'NIPA', file 'NIPA_log' on file 1.
      BACKUP LOG successfully processed 33136 pages in 3.697 seconds (73.423 MB/sec).

4. Once you see this message type in the following.

   1> dbcc loginfo(nipa)
   2> go
  This will display a long list and the far left column is where you will either see 0 or 2.
  Example of 2:     2            5570560            224526336    200
            0    64        1960000000961100001   

  Example of 0:     0            5570560            224526336    200
            0    64        1960000000961100001   

5. After running this wait about 5 minutes and then type exit to logout of the SQL.

6. Go to Windows Services and stop the MSSQLSERVER service.

7. Wait about 2 minutes and then Start the MSSQLSERVER service

8. repeat steps 2 through 4

9. No wait is needed this time, begin typing the following:
   1> dbcc shrinkfile (NIPA_log,10)
   2> go

   Note: You should get the following message below with no errors. 
   DbId   FileId CurrentSize MinimumSize UsedPages   EstimatedPages
   ------ ------ ----------- ----------- ----------- --------------
       5      2        1303         128        1296            128

  (1 row affected)
  DBCC execution completed. If DBCC printed error messages, contact your system

! 1> dbcc shrinkfile (NIPA_log,10)
! 2> go
! Msg 8985, Level 16, State 1, Server IPCELERATE1, Line 1
! Could not locate file 'NIPA_log' in sysfiles.
! DBCC execution completed. If DBCC printed error messages, contact your system
! administrator.

10. Verify the NIAP_log.LDF file under C:\Program Files\Microsoft SQL Server\MSSQL\Data is rougly 10MB, if not repeat step 9 again.

11. Type the following to exit SQL:
    1> exit

12. Start the following services in this order:
    Apache Tomcat Tomcat5