inspirednetworks
asked on
ASCL failed to initialize - BLACKBERRY ENTERPRISE 4.1 UPGRADE FROM 4.0
Hi There,
I upgraded from a perfectly working copy of 4.0 to 4.1 today and am now getting a "ASCL failed to initialize" error when i attempt to get into "Blackberry Manager"
I tried deleting the MAPI profiles but that didn't seem to do anything...
Here is what i can get from the logs:
DBUtil::initASCL(): ASCL failed to initialize
BlackBerry Manager has failed to initialize. Shutting down...
Any help is much appreciated!
I upgraded from a perfectly working copy of 4.0 to 4.1 today and am now getting a "ASCL failed to initialize" error when i attempt to get into "Blackberry Manager"
I tried deleting the MAPI profiles but that didn't seem to do anything...
Here is what i can get from the logs:
DBUtil::initASCL(): ASCL failed to initialize
BlackBerry Manager has failed to initialize. Shutting down...
Any help is much appreciated!
Recreate your outlook profile from scratch and try again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up just reinstalling windows and BES, works great now!!!
It was a problem with bb desktop manager though right?
ASKER
No, the problem was with the MAPI subsystem... There were corruptions in the whole Exchange System Manager installation, causing the services to die. I'm not even using desktop manager, my blackberries just sync right over the wireless network. Alot of the problems were rooted back to that 4.0 can work using the MAPI subsystems included in Outlook 2003, while 4.1 requires that System Manager be installed.
Just a little bit of insanity, now its working... my suggestion to ANYONE trying to get BES working properly and error-free... start with a FRESH Windows 2003 Server installation... Install Exchange System Manager, SQL Server 2000 SP4, THEN install BES 4.1 (and Java)
Pce out. Scott.
Just a little bit of insanity, now its working... my suggestion to ANYONE trying to get BES working properly and error-free... start with a FRESH Windows 2003 Server installation... Install Exchange System Manager, SQL Server 2000 SP4, THEN install BES 4.1 (and Java)
Pce out. Scott.
ahh, that same _exact_ thing happened to me actually. I was under the impression you were having problems with desktop manager, not bb manager.
and yes, always start fresh...especially when dealing with anything critical that is based on java!
and yes, always start fresh...especially when dealing with anything critical that is based on java!