Goodlink Error 19
Contents |
server service fails to start with "Windows could not start this device has already been provisioned hbo the GoodLink Server on Local Computer.For more information, review the
Already Set Up Synonym
System Event Log..." and the following series of events 3515,6514, and 10253 in the app
This Device Has Already Been Set Up For Another User Good
logPrintable View «Go Back SituationGoodlink server service fails to start with following error"Windows could not start the GoodLink Server on Local Computer.For more information, review
That Fingerprint Has Already Been Set Up On Another Account
the System Event Log..."and the following series of events appear in the system event log3515 The following information was included with the event: some thread id6514 The following information was included with the event: Initialize failed for Good Messaging Server. (errWSEDBFail), [11]10253 The following information was included with the event: Good Messaging good for enterprise troubleshooting Server initialize errWSEDBFail Other symptoms Folders such as TZDB_log PoisonMsgHandler_log and files like poison.db and handhelds.db may not be recreated on attempting to start if renamed or deleted.GdBDBRecovery.exe -resetlsn -deletelogs fails with2013-01-04 19:31:15 BDB_Error:server2 c:\program files (x86)\good technology\good messaging server\cache\
frequently Product Advisory: GFE GMMS servers abnormally restarting Goodlink service restarts frequently after upgrade to version 7.2.0.53 Can't good for enterprise support find what you need? Contact Us Other Resources BlackBerry Knowledge Base Good Admin Portal Good Online Portal (GFE) What would you like to know? Reset Search Search < Back to search results GoodLinkServer service crash & restart repeatedly. Application Event ID 2566, System Event ID 25Printable View «Go Back SituationThe Good link server service http://goodpkb.force.com/PublicKnowledgeBase/articles/Answer/2381 has repeatedly crashed and restarted about every half hour. The server has over nine hundred active devices.Copy of eventEvent Type - ErrorEvent Source- Goodlink ServerEvent ID - 2566Date- 8/11/2012 Time - 5:46:19Description:Thread dowork-5 (103297328) (dowork2_0) caught an unexpected structured exception type 0xe06d7363. Stack backtrace follows: RaiseException +00060 bytes _CxxThrowException +00070 bytesstlp_std::__stl_throw_length_error +00197 bytesCopy of EventSource - VolsnapDate - 8/14/2011Time - 5:46:19 pmEvent ID- 25Description:The shadow copies of volume C: were http://goodpkb.force.com/PublicKnowledgeBase/articles/Answer/1249 deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadowed copied.What changed: 5-15 users a day added to the GMMExpected Result: continued mail flowActual Result: paused users due to goodlink service crash and restart EnvironmentGMM version: 7.0.0.6Server configuration: GMM/GMC on same server, remote SQL, remote cache both on D drive fiber attached SAN using shadow copy on D driveGood server OS: Server 2003 Standard 32 bit Solution1. For Application Event ID 2566 open a new incident from the GMP and upload GMM and GMC server logs. Please refer to article How to upload diagnostics logs2. For System Event ID 25 as the GMM thresholds of number of users per GMM server are reached user cache corruption can occur causing the goodlink server service to restart. Remove users from the GMM until the service stabilizes.3. For System Event ID 25 verify the cache folder is excluded from any program that can conflict wit
Contacts My Profile Mark Forums Read 0 New Home Forum webOS Devices Palm OS Devices & Apps Another Goodlink Fatal Error Results 1 to 11 of 11 Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode conekkted Posts http://forums.webosnation.com/palm-os-devices-apps/136610-another-goodlink-fatal-error.html 337 Posts Global Posts 366 Global Posts 02/11/2007,11:01 AM #1 Lowdown - I am using GMM 4.9.2.30_EN on a Windows Mobile Treo 750. GMM was the last third-party app installed and has been running for about 2 weeks. Last week I started getting a fatal error message while composing emails in GMM. It happened once or twice a day. The error reads: Fatal Error Exception [c0000005] at address 3fb2d60, program exiting. When I "OK" the error window it shuts down GMM. has already And I mean shuts it down, not just hiding the email app but removing GoodApp.exe from memory ( ironic, because that's a feature that Good has not figured out how to do). Well now I have found out that it is not just related to composing email. I think it has to do with times when GMM is trying to access the server. The reason I say this is that the error will sometimes be on the screen when I go to turn has already been my device on. In other words when I am not using the device. So the only thing that is going on when I am not using the device is GMM looking for new mail to push from our server. And I know it is GMMM related because even if I have multiple apps open, the error always shuts down GMM and nothing else. Anyone else having this error? Treo 750 - Cingular/ATT Reply evilgrimace Posts 19 Posts Global Posts 20 Global Posts 02/19/2007,12:50 PM #2 yup! Have used my new 750 with Good for 2 weeks then this weeken BAM! Fatal errors abound! I thought that switching between GSM and UMTS would be the issue. But now on GSM for two hours and two Fatal Errors. Version: GMM v4.9.2.30_EN Software: TREO750-1.13-CNG Hardware A Firmware 1.17.20.00 I know we need to go to 4.9.3 for DST but my guess is that won't help. Reply conekkted Posts 337 Posts Global Posts 366 Global Posts 02/19/2007,05:01 PM #3 Thanks for taking the time to corroborate my issue. What other 3rd party apps or hacks do you have on your device? This has actually become more of a business impact than an annoyance. Sometimes it shuts down on me in the middle of composing a long email. But mostly it happens when I am not active and I turn on my device only to be welcomed by the error and have GMM shut down. The erro