blackberry 4.0
i have blackberry package fine the problem is went you check on configure pim i get a error stating that there is a "internal error"
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
linstead
19 years ago
Posted by:
plangton
19 years ago
Posted by:
brenthunter2005
19 years ago
Correct me if I'm wrong, but the "Internal Error" linstead is talking about isn't MSI related. Its the actual Blackberrg application producing this error message, right?
If so, its because the neccessary COM servers haven't been registered properly. Remember that with the Blackberry software you probably need to perform "/regserver" on the .EXE files.
Let me have a look and get back. [sm=rolleyes.gif]
If so, its because the neccessary COM servers haven't been registered properly. Remember that with the Blackberry software you probably need to perform "/regserver" on the .EXE files.
Let me have a look and get back. [sm=rolleyes.gif]
Posted by:
linstead
19 years ago
Posted by:
sean_c_roberts
19 years ago
Hehe - when WE were working on the BlackBerry desktop (versions 3.6 and 4.0, I believe) the MOMENT we say that there were COM components too it, we KNEW we could not repackage it...
Also, the MSI (which means you should not repackage it in ANY case) has been coded to require the setup.exe - and there is an InstallShield article about how to get around that, but...
All in all, your best bet is to wrap this app in a Wise exe and use the native install...
Also, the MSI (which means you should not repackage it in ANY case) has been coded to require the setup.exe - and there is an InstallShield article about how to get around that, but...
All in all, your best bet is to wrap this app in a Wise exe and use the native install...
Posted by:
plangton
19 years ago
Brent,
Yep thats right, its not an MSI error but if you've run into lots of blackberry issues theres lot of different internal codes it may or may not spit out. I suspected it was the error you detailed as I've run into it but there are others you can run into depending on configuration etc.
Sadly I can't help much with the deployment via active directory, I've done it for Zenworks, Altiris and SMS2 and had no deployment related issues.
Rgds
Paul
Yep thats right, its not an MSI error but if you've run into lots of blackberry issues theres lot of different internal codes it may or may not spit out. I suspected it was the error you detailed as I've run into it but there are others you can run into depending on configuration etc.
Sadly I can't help much with the deployment via active directory, I've done it for Zenworks, Altiris and SMS2 and had no deployment related issues.
Rgds
Paul
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.