Notifylink Error Code 557

Web Server (19)NotifyLink Database Component (1)NotifyLink Multi-Tenant Edition (5)NotifyLink On Demand (4)Sales (2)NotifyLink Patch Installer (48)NotifyMDM Server (108)NotifyMDM Device SEARCH Knowledgebase: BlackBerry Error Codes when syncing or registering Posted by - NA - on 06 July 2009 01:18 PM BlackBerry:Errors seen when registering or syncing on a Blackberry:1. "net.rim.devce...wap.http"** This error may mean either the incorrect network setting is chosen on the phone or the phone is out of data coverage. The device may not have coverage due to issues with the carrier or the customer may be in an area where data service is low. You can try soft resetting the device to reset the network connections. ** If it is a matter of the incorrect network setting then please ensure you have the correct WAP chosen for your carrier. To select this you would go into Email, click the scroll wheel and choose Preferences, then highlight Network Setting and choose Change option and select your carrier from the list. If you have chosen your specific carrier's network setting and it does not work for you, you can try using either TCP or Blackberry.2. "NotifyLink could not establish a network connection" ** This error may refer to a loss of data coverage. The device may not have coverage due to issues with the carrier or the customer may be in an area where data service is low. You can try soft resetting the device to reset the network connections.3. "java.lang..." ** This error usually refer to the databases on the device or a problem reaching the HWP page for the device. First,try resetting the device. Also check the HWP for the device to ensure there is not an extremely large quantity of items waiting for the phone. Help Desk Software by Kayako

PowerVM virtual I/O server VIOS led reference code 551 555 557 boot up failure failed hang hanging hung Technote (troubleshooting) Problem(Abstract) This document discusses the most common causes for reference code/LED 551, 555, or 557 during boot up, and common recovery procedure. Symptom VIOS fails to boot up with reference code 551, 555, or 557 Cause A corrupted filesystem in VIOS rootvg A corrupted journaled file system (JFS) log device in rootvg Hardware component failure (i.e. disk, adapter, etc) related to VIOS rootvg Environment PowerVM VIOS 2.2 or higher Diagnosing the problem Login to the VIOS management GUI (i.e. HMC, FSM, etc), select the VIOS partition and look at the Reference Code. 551 indicates VIOS rootvg activation (varyon) 555 means fsck error, fsck failure of / (root) filesystem, http://support.notifycorp.com/support/index.php?/Knowledgebase/Article/View/557/25/error-codes-when-syncing-or-registering /dev/hd4 557 means failure to mount / (root) filesystem Resolving the problem To diagnose and attempt to fix any of these reference codes, you must boot the VIOS partition into maintenance mode to run a thorough file system check (fsck) and reformat the jfs2log, /dev/hd8. 1. Boot VIOS partition to maintenance mode and choose the following option: Access this volume group and start a shell before mounting the filesystems (option 2) This option will attempt to import the VIOS rootvg in a limited shell (with http://www.ibm.com/support/docview.wss?uid=isg3T1022728 no filesystems mounted). Pay close attention to the output as this is the point where I/O errors are commonly seen when the issue is due to an underlying hardware problem related to rootvg, i.e. Fatal: I/O error If you get errors at this point indicating that a physical volume is missing from the rootvg or errors suggesting a hardware component failure, such as the "I/O error", do not continue with the rest of the steps in this document. Run diagnostics or contact your local Hardware Support Representative. 2. Format the default jfs2log for the VIOS rootvg if the volume group is successfully imported: /usr/sbin/logform /dev/hd8 Answer yes when asked if you want to destroy the log. 3. Next, run fsck to check and repair file system corruption. (The -y option gives fsck permission to repair file systems when necessary.) fsck -y /dev/hd4 / (this is the root filesysem) fsck -y /dev/hd2 /usr fsck -y /dev/hd9var /var fsck -y /dev/hd3 /tmp fsck -y /dev/hd1 /home fsck -y /dev/hd10opt /opt fsck -y /dev/ hd11admin /admin fsck -y /dev/ livedump /var/adm/ras/livedump 4. Type exit . The file systems will automatically mount after you type exit. 5. If the VIOS is hosting AIX clients' rootvg on virtual SCSI disk backed by an hdisk, you can verify at this point that the volume group selected e

may be temporarily blocked from locations that fetch an unusually high number of pages. We apologize for the inconvenience.