Hi,

I am trying to upgrade my BES 4.0.4 hf3 to BES 4.1 Express. After starting setup.exe I get the following error:

Setup.exe - Application Error
The instruction at "0x7c836d25" referenced memory at "0x00000000". The memory could not be "read".

And the Eventlog shows this error:
Faulting application Setup.exe, version 1.0.0.1, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x00036d25.

After a while I get this message as well:
rPIPTool MFC Application
rPIPTool MFC Application encountered a problem and needed to close

This BES server is running fine, I do not have a single problem with it until now. I can't find any reference to this error in combination with a BES install, nor can I find anything about rPIPTool MFC.

Thanks in advance.

BES 4.0.4 HF3 - is that full-blown BES or BES SME/SBE?

That is a SBE version.

is the BES Express able to upgrade an existing version? see if it has an Upgrade Guide and look in it for pre-reqs. i can definitely see a reason they'd build some level of upgrade-proof abilities into the free software and lock you into having to purchase TSupport or the one-time upgrade fee to get 4.1.

I have the exact same problem ... But I am on a new server ... Win2k3 with Service Pack 1, Exchange, Domain Controller and it has Trend Micro Small Business...

Anyone know how to resolve this issue?

I have successfully upgraded a BES 4.0.0 for Exchange installation to 4.1 Express. The upgrade components (database upgrade & user migration) are included in 4.1 Express. You just throw away the licensing information you got with 4.1 Express as it automatically uses the BES 3.6 or BES 4.0 licensing information.

I have not found a solution yet....

Hi sddroog..

I finally got it to work!! I had to double-click on the setup.exe icon about a 20-30 times until finally the wizard popped up ...

... There is another issue ... After you get the wizard to pop up and it does the first phase of the install it may require a reboot to complete. Well, when it reboots and you log back into the server it has to reload setup.exe. And it has a problem doing it again, so you have to logoff/logon until it finally starts up. I actually logged off/on about 10 times before I gave up and started double-clicking on setup.exe a 20-30 more times.

Let me know your result. I just did this on a production server and ofcourse had a full backup of everything.

Also, just an FYI, I manually created a new BESMgmt database using the BES scripts. I don't recommend you trying that since you are doing an upgrade. I just happen to know how to install a new database without utilizing the setup wizard.

It does work (but I needed 200 to 300 tries before it would start!) but now I have a new problem which I don't think is related. After the setup.exe restarts (after restarting the server) and entering the license key it says "Failed to write License key to the Database.". It doesn't matter if I try my 4.0 license key or the key that I got with 4.1.

Help?

Ok, I found some additional information in the logfile:

[30000] (06/02 08:41:59):{0x13DC} Current Date: 2006/06/02
[30000] (06/02 08:41:59):{0x13DC} [DIAG] EVENT=Thread_report, THREADID=0x13DC, THREADNAME="DebugLogger"
[30000] (06/02 08:41:59):{0x13DC} [ENV] Current Process: C:\rim\BES4.1.0\Setup.exe
[30000] (06/02 08:41:59):{0x13DC} [ENV] Current Process logged on as: HADAPSY\BesAdmin, Start Time: Jun 02 2006 08:41:59, Uptime (seconds): 0
[30000] (06/02 08:41:59):{0x13DC} [ENV] Current Process id: 4740
[30000] (06/02 08:41:59):{0x13DC} [ENV] Computer Host Name: HADAPSY001, OS Version: 4.0, Build number 950, ServicePack Major 1, ServicePack Minor 0
[30000] (06/02 08:41:59):{0x13DC} [ENV] Processor Identifier: x86 Family 15 Model 3 Stepping 4
[30000] (06/02 08:41:59):{0x13DC} [ENV] Processor Vendor Identifier: GenuineIntel
[30000] (06/02 08:41:59):{0x13DC} [ENV] Processor Name String: Intel(R) Pentium(R) 4 CPU 3.00GHz
[30000] (06/02 08:41:59):{0x13DC} [ENV] Number of Processors: 2
[30000] (06/02 08:41:59):{0x13DC} [ENV] 30 percent of memory in use.
[30000] (06/02 08:41:59):{0x13DC} [ENV] Total size of physical memory: 2088208 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Size of physical memory available: 1453040 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Size of the committed memory limit: 5088588 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Size of available memory to commit: 3988936 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Total size of the user mode portion of the virtual address space of the BES process: 2097024 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Size of unreserved and uncommitted memory in the user mode portion of the virtual address space of the BES process: 2040632 KB
[30000] (06/02 08:41:59):{0x13DC} [ENV] Total HD bytes: 120023252992, Total free bytes = 76854317056
[30000] (06/02 08:41:59):{0x13DC} [ENV] System up time: 0 days 00 hrs 35 mins 04 secs
[30000] (06/02 08:41:59):{0x13DC} [ENV] TCP/IP provider (Winsock) File Version: 5.2.3790.0 (C:\WINDOWS\System32\wsock32.dll)
[30000] (06/02 08:41:59):{0x13DC} [ENV] Unable to provide HostName
[30000] (06/02 08:41:59):{0x13DC} [ENV] Winsock2 file: Tcpip, Version: 5.2.3790.1830 (C:\WINDOWS\System32\mswsock.dll)
[30000] (06/02 08:41:59):{0x13DC} [ENV] Microsoft XML Parser 4.0: C:\WINDOWS\system32\msxml4.dll, Version: 4.20.9818.0
[30000] (06/02 08:41:59):{0x13DC} [ENV] MDAC version: 2.82.1830.0
[30000] (06/02 08:41:59):{0x13DC} [ENV] MSADO15.DLL: C:\Program Files\Common Files\System\ado\msado15.dll, Version: 2.82.1830.0
[20000] (06/02 08:41:59):{0x157C} COM Error 0x80004005 in ConnectionItem::ConnectToDB() - Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. - Unspecified error (connection string - Provider=SQLOLEDB;Server=HADAPSY001;Database=BESMg mt;Trusted_Connection=Yes)
[20651] (06/02 08:41:59):{0x157C}
[30000] (06/02 08:41:59):{0x157C} [PIPTOOL]: Entering LicenseProxy.

I think the problem is that setup.exe is unable to access the database with user 'null'. But I am not a database expert. I am using MSDE.

Thanks again.

Ok, I was able to fix the database problem with help of this KB article: http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/8021/728075/728850/728953/Support_-_Login_failed_for_user_'(null)'.html?nodeid=106210 5&vernum=0

To bad the "Application error" comes back while trying to upgrade the mds database! grrr....

Try this for me:

http://support.microsoft.com/kb/555175/en-us

I didn't completely work for me but it was the closest I came to finding a solution. I did eventually get it installed, the way I told you earlier (review higher up in this thread.) ...

Did you try what I told you earlier?

Just curious

Single... Dual capable.

any new resolutions here? Getting the same error and not having any luck.

Basically .. Keep executing the program until it finally starts .. I think BlackBerry support needs to be aware of the issue. I am willing to be part of a support call if you want to gather more people who have had the issue.

I no longer need to run setup since I finally got it to work after clicking about 100 times.

on the phone with RIM and they have no clue what the error is!!!


Ah yes, always fun stuff!!!

Has anyone worked out how to get round this?

I'm trying to install BES4.1 for Exchange on a clean WS2003 image, the setup.exe will not start it just crashes giving th rPIPtool error and/or dumping a Dr Watson crash log.

It's starting to drive me nuts!

I've tried the keep clicking on it approach to no-avail.

I truely don't know what to tell you... It's an error message that has never come up in any other installation program except this one. So there is not even general information related to it. There must be an underlying issue that is not immediately evident. Do you have the latest Service Packs, etc installed on the box? Can you tell us about the hardware? Maybe it has something to do with a device driver, like the COM port drivers. Try disabling the COM ports, etc..

Bradley

RIM told me it might be a windows installer issue. Since I am the only user at the office I uninstalled the old 4.0 version, reinstalled and used the keys they gave me for 4.1 express. Asked tech support and they said I could use thos keys with any version.

Let me know if you try to updated windows installer and that solves your problem. Obviously something is going on.

SGM-CO

I agree that it is quite possibly the windows installer. I posted the article: http://support.microsoft.com/kb/555175/en-us from Microsoft Support early in this thread. That didn't work for me, but maybe it will work for you. I also tried to install a different application that using MSI, and it worked fine.

By the way, I already installed and got past this issue. I just double-clicked the setup file a thousand times. I'm still interested in finding out what the issue is since the client that had this issue is still a client and I will one day need to do something with BES on that server.

Bradley

Well I've managed to get it installed. I'm using a Windows Server 2003 image (under virtual server R2). I disabled as many services as I could.

It is very odd. Over two days of trying with 2003 Server it would magically start working (the install dialog coming up rather than crashing) late in the afternoon after 5pm local time. Yes very odd.

However I got caught at the second stage where you have to reboot and run setup.exe again - it wouldn't work. I had already turned as many services off as I could. I then tried disabling the network interface and the installer magically worked!!

It has taken me days to get this far, I've tried Windows 2003, Windows 2000 and XP images - I eventually gave up with 2000 & XP I'd updated the Windows Installers. I seemed to be able to get furthest with 2003 Server and then it just started working!

There is something very wrong with the BES installer.

Great advice everyone.

I have been battling with this problem for a while and still haven't been able to figure out what's causing it.

I got round it by double clicking Setup.exe, then double clicking again immediately afterwards (almost instantly) - worked every time.

Let me know how you all get on.

Nick

I was on the phone with RIM about this issue, and they said that if you have a NIC with two IP Addresses on it, it could cause the problem... It fixed it for me on my test server.

Hope this helps...