Article ID: 18413
Audience: Public
Product: Good Mobile Messaging Server
Date: 16 January 2009
Date Updated: 11 March 2009

Title: Good Messaging Server service will not stay started.

Symptom: Trying to start The Good Messaging Server, it will stay started for a few seconds and then crashes with the following application event error.

Event Type: Error
Event Source: GoodLinkServer
Event Category: (12)
Event ID: 3510
Date: 3/11/2009
Time: 6:56:19 AM
User: N/A
Computer: GOODLINKServer
Description:
Good Messaging Server failed to initialize session manager. (SESSION ERROR GDERR_INTERNALERR) (Context create)
 

Event Type: Error
Event Source: GoodLinkServer
Event Category: (12)
Event ID: 3507
Date: 3/11/2009
Time: 6:56:19 AM
User: N/A
Computer: GOODLINKServer
Description:
Good Messaging Server synchronization engine failed to initialize. (ERROR errWSEInitFailed)
 

Event Type: Error
Event Source: GoodLinkServer
Event Category: None
Event ID: 6514
Date: 3/11/2009
Time: 6:56:19 AM
User:
Computer: GOODLINKServer
Description:
Initialize failed for Good Messaging Server. (errWSEInitFailed), [14]


Event Type: Error
Event Source: GoodLinkServer
Event Category: (25)
Event ID: 10253
Date: 3/11/2009
Time: 6:56:19 AM
User: N/A
Computer: GOODLINKServer
Description:
Failed to start Good Messaging Server. Operation initialize failed with error errWSEInitFailed.

Host machine experienced disk issue around the same time.

Looking In the gtinemo.log file, which is located in the Good Messaging Server log directory, the following error message was present: (this log file is text based)

14:10:37:0000:: 18fd080:: msgsock:: event::GTI:Use connect/select.
14:10:37:0000:: 18fd080:: dbmngr:: error::GTI:failed to read record line in deSerializeFile

Cause: This error "SESSION ERROR GDERR_INTERNALERR" indicates  the Good Server is unable to contact or login to the datacenter.
With the error in gtinemo.log "dbmngr:: error::GTI:failed to read record line in deSerializeFile" the database in-use by the gti layer might be corrupted.

Resolution: Please do the following:

1. Open explorer and navigate to the following location:

C:\Program Files\Good Technology\Good Messaging Server\cache\<SERVER>

2. Make a backup copy of the following files to another location.
db.db
poison.db
server.gd

3. Delete the db.db file from C:\Program Files\Good Technology\Good Messaging Server\cache\<SERVER>

4. Re-install the GMM Server

5. Start the GMM Server.

Delete the db.db

It is safe to delete this file as the GTI logic will recreate the database file.

Additional Info: Normally when there are issues with service restarts one has to set cachesize to 0 and reproduce the problem.