jriggy
asked on
Error 1606 Cannot access network location cccc Wile upgrading BES Software
I am getting the following error while installing the upgrade to Blackberry Enterprise Server 4.0.7 from 4.0.6.7
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11606
Date: 3/17/2009
Time: 2:11:28 PM
User: ATL-WHATSUP\Administrator
Computer: ATL-WHATSUP
Description:
Product: BlackBerry Enterprise Server for Microsoft Exchange -- Error 1606.Could not access network location cccc.
I have looked at numerous posts about error 1606 but nothing seems to fix my issue. I have even attempted to use another profile (local admin) to install with no success.
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11606
Date: 3/17/2009
Time: 2:11:28 PM
User: ATL-WHATSUP\Administrator
Computer: ATL-WHATSUP
Description:
Product: BlackBerry Enterprise Server for Microsoft Exchange -- Error 1606.Could not access network location cccc.
I have looked at numerous posts about error 1606 but nothing seems to fix my issue. I have even attempted to use another profile (local admin) to install with no success.
ASKER
the BES software is on the C: drive. Nothing out of the ordinary... Thats why this is bugging me!
What I meant was that in the error you have posted "Could not access network location cccc", I guess that cccc is a munged path, so what is that path?
It is probably looking for the original installation location.
-M
It is probably looking for the original installation location.
-M
ASKER
The path is the default selected by the original BES 4.0 installer:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server
C:\Program Files\Research In Motion\BlackBerry Enterprise Server
Do you have the original installation CD etc available?
-M
-M
ASKER
yes....
ASKER
what do you recommend?
Putting the original CD in to the drive would be a start.
Another option would be to reinstall BES on top of the existing installation.
-M
Another option would be to reinstall BES on top of the existing installation.
-M
ASKER
LOL.....Thanks Mestha... I will give that a shot... I will let you know how it turns out!!
Hi, just make sure you BlackBerry Service Account (e.g. BESadmin) is a local Administrator on the server BES is installed on. If this BES is installed on a domain controller this is done by adding the user to Built-in > Administrators. On some occasions it can be caused by a corruption in the installation package so you have to:
1. Ensure you have a copy of the full BES installer (call you carrier support and they can escalate you to RIM to get a full 4.0.7 installer)
2. Uninstall BES 4.0, if it can't be removed use "Windows Cleanup" utility (then manually delete the registry entries)
3. Reinstall BES and point it back to the existing database
1. Ensure you have a copy of the full BES installer (call you carrier support and they can escalate you to RIM to get a full 4.0.7 installer)
2. Uninstall BES 4.0, if it can't be removed use "Windows Cleanup" utility (then manually delete the registry entries)
3. Reinstall BES and point it back to the existing database
ASKER
OK, We will give that a try. I just have to do it on the weekend in the middle of the night to avoid peak hour service interruption.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
-M