08-04-2008, 07:49 PM
|
#1 (permalink)
|
| Knows Where the Search Button Is
Join Date: Mar 2008 Model: 8130 PIN: N/A Carrier: AT&T
Posts: 39
Post Thanks: 0 Thanked 0 Times in 0 Posts
|  GWSoapConnector error
Please Login to Remove! Today for some reason my BES decided to throw a fit, I keep getting the below errors:
The description for Event ID ( 14143 ) in Source ( GWSoapConnector ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {4} {User Name} Flush Events: Failed, Ids=15997, 15998, 15999, 16000, 16001, 16002, 16003, 16004.
The description for Event ID ( 14140 ) in Source ( GWSoapConnector ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {0} {User Name} Folders: Error=Missing Calendar Folder.
We did have an issue with Groupwise today and it has since been resolved. However for some reason the BES is deleting all email from the users handhelds/accounts. The reason given by RIM is that the POA and the BES got so out of synch that it is deleting everything and re-synching with Groupwise. So I have no email from before 1pm PST (even though I had stuff on there from over the weekend this morning), one user even said that as he was replying to an email the email itself got deleted. From my understanding this is not expected behavior, okay if the Post Office was down for a little bit I would expect any new mail to be delivered to the handheld once service was restored, not delete ALL of the old email!
RIM suggested that I just wait and see if the server synchs back up, okay and then what if it doesn't? WTF? I decided to post here and see if anyone else has seen this issue before. Most of the articles I have found that remotely mention something similar with the SOAP connector is that the wrong SOAP port was specified or SOAP is not enabled. That doesn't apply in this case, we are using the correct port and have been running on SOAP flawlessly since April. Any ideas people, I know this is probably just a shot in the dark but I got nothing to lose at this point.
Last edited by ELBeast : 08-04-2008 at 07:54 PM.
|
| Offline
| |
