Database Size Grows Exponentially When Thousands of Registration Notification Messases Logged

Article:TECH88539  |  Created: 2006-01-16  |  Updated: 2011-08-30  |  Article URL http://www.symantec.com/docs/TECH88539
Article Type
Technical Solution

Product(s)

Issue



 Any of the following symptoms may occur:

  • Database may grow in size exponentially.
  • Users cannot login or send messages.
  • Policy Action report shows thousands of Blocked Login Enforcements.

To verify follow these steps:

1. Open the IM Manager Administration Console.

2. Click on Status tab.

3. In the Policy actions summary field, the Login field listed for Today is many thousands.

  • MSMQ on the local IM Manager server may store messages at rates of thousands per minute.
  • The IM Manager system may become unreliable/unresponsive.
  • The IMLogRelayService is using up more then 95% of the CPU

    To verify follow these steps:

    1. Open the Task Manager on the server where IM Manager is installed.

    2. In the Image name column find IMLogRelayServce.

    3. Having the CPU listed as consistently at or above 95% incates this symptom

  • There are many unexpected notifications or disclaimers appearing in the Reviewer interface for each conversation.
  • IM Manager System Dashboard Takes a Long Time to Display Or Does not Display Correctly: Active Server Pages error 'ASP 0113'
  • In the Windows Application Event log there are many errors similar to the following:


Type :  Error
Date :  5/24/2010
Time :  8:23:48 PM
Event :  100
Source : Symantec Components
Category : None
User :  IMM_Account
Computer : IMMANAGER01
Description:
MSMQ is not available or quota has been exceeded (-2147023080)

  • There are database errors shown in the Windows Application Event log reporting that the database is full like this message:

 

 

 

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.ImpactTracking' in database 'IMManagerDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.-42000
 

 

 

 


Conditions

  1. Require Registration policy is enabled.

1. Open the IM Manager Administration Console.
2. Click on Policies tab.
3. Click on General Policy > Registration menu item.
4. If the value of User Registration > Require IM Screen Name Registration is checked then users must be registered to send or receive IM Messages.

  • Notifications are enabled for require registration.  
    1. Open the IM Manager Administration Console.
    2. Click on Policies tab.
    3. Click on General Policy > Registration menu item.
    4. If the value of User Registration Notification > Send Notification when user is not registered is checked then the notifications are sent and logged by IM Manager.
  • There is a whitespace at the end of the registration message.

1. Open the IM Manager Administration Console.
2. Click on Policies tab.
3. Click on General Policy > Registration menu item.
4. The message in one of the textboxes for Send notification when user is not registered has a whitespace at the end.  This could be a carriage return or newline or a space or tab.


Cause



IM Manager prevents duplicate notifications by comparing the incoming/outgoing messages with the registration notification message.  If they "match" then the notification is not sent again.  When there is a whitespace at the end of the notification this matching capability fails and IM Manager sends a second notification message.  This then continues indefinitely.


Solution



Upgrade to IM Manager 8.4.17 or later.

Workaround

Remove Whitespace from the Notification Message

1. Open the IM Manager Administration Console.
2. Click on Policies tab.
3. Click on General Policy > Registration menu item.
4. Remove any whitespace present at the end of the message in one of the textboxes for Send notification when user is not registered.  This could be a carriage return or newline or a space or tab.

 NOTE:  Use the following article to reduce the size of the IM Manager database: The Size of the IM Manager Database is Large. How do I Manage it?

Technical Information

  • Use a SQL query to find IM conversations affected by this issue.

Run the following SQL query against the IM Manager database.  Before running the query replace the date ranges with ones appropriate to your environment:

SELECT     CONVERT(varchar(100), message_date, 1) AS day, session_guid, COUNT(id) AS numberofmessages, SUM(DATALENGTH(content)) AS totalcharactersizeofconversation
FROM         messages
WHERE     (message_date BETWEEN '5/24/2011' AND '6/10/2011')
GROUP BY CONVERT(varchar(100), message_date, 1), session_guid
ORDER BY count(id) desc

 

The conversations with the highest number of messages are returned first.  The following is an example:

    03/07/06    CHAT-569596-195832-1141774369182079-2006-03-07    152037    1272010
    01/24/06    105264628954270397-2006-01-24                                       1863    168498
    03/03/06    CHAT-3873956-111550-1141343538852493-2006-03-03    1672    67088
    03/08/06    CHAT-569596-195832-1141774369182079-2006-03-08     1644    128012
    03/08/06    CHAT-3675299-2447959-1141778724282493-2006-03-08  1000    67750
    01/24/06    109463918914598245-2006-01-24                                         986    112346
    10/03/05    CHAT-569596-446801-112829837499853-2005-10-03        968    376400
    02/15/06    CHAT-569596-446801-1140044671198566-2006-02-15      861    703942
    01/18/06    10359780288987424529-2006-01-18                                    696    37758
    03/03/06    CHAT-2447959-3675299-1141357895219565-2006-03-03  660    41004
    01/18/06    105264628954270397-2006-01-18                                         615    41000
    03/03/06    CHAT-3090042-3627259-1141345483334827-2006-03-03  605    129556
    03/08/06    CHAT-3791713-2447959-1141776575199629-2006-03-08  604    39376

In this example above the first conversation contain over 150,000 messages.  It is likely that conversation is affected by this issue. 

Use the following SQL to view the first 2000 messages in the conversation:

Select top 2000 * from messages where session_guid = ‘CHAT-569596-195832-1141774369182079-2006-03-07’

The message details are in the messages.content column.  If these messages are all notification messages then this conversation is affected by the issue.  The following are examples of content like this:

<FONT COLOR="#0000FF" LANG="0" SIZE="2"><B>IM Administrator: </B>This recipient is not permitted to use IM.</FONT>
<FONT COLOR="#0000FF" LANG="0" SIZE="2"><B>IM Administrator: </B>You cannot login to the IM Network because you have not registered your IM screen-name. Check with your IM administrator for IM registration procedures.</FONT>

 

 

 

 

 


Supplemental Materials

SourceETrack
Value1497619, 10400

SourceEvent ID
Description

Type :  Error
Date :  5/24/2010
Time :  8:23:48 PM
Event :  100
Source : Symantec Components
Category : None
User :  IMM_Account
Computer : IMMANAGER01
Description:
MSMQ is not available or quota has been exceeded (-2147023080)


SourceEvent ID
Description

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.ImpactTracking' in database 'IMManagerDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.-42000
 


Legacy ID



2007884101033298


Article URL http://www.symantec.com/docs/TECH88539


Terms of use for this information are found in Legal Notices