[jamesh]

Hi,

I am trying to invoke setup.exe from my new 4.1 install (it's an upgrade but it doesnt get anywhere to care at this stage).

When we click the setup.exe the file loads briefly (as seen in the task manager) and then closes. We have enabled window installer logging but nothing is reported either there or the event logs.

We have tried this on a W2k server and a w2003 server with the same problem. We have also tried it on yet another w2k server and it loads fine!

It seems to have started when we abandoned the install due to some db upgrade probs which we believe are sorted.

We have also followed some threads here on how to clean up the windows installer but to no avail!

Any help would be much appreciated.

Many thanks.

James.

[Bill_theITguy]

I had a nightmare of a problem that I finally resolved by doing two rather odd things.

First, my Performance counters all had to be disabled due to (I think) some IBM Workplace Services Express software that did not uninstall cleanly.

Second, I needed to disable BMC Patrol which is installed on many Dell Servers (probably other brands as well - I just know Dell).

Easiest way to tell if BMC is your problem? Physically disconnect all patch chords, restart the server and then launch install. If install finally runs, you're in business.

At some point during install, BES needs to test connection to Blackberry's SRP server. At this point just plug in the patch chords, click on the Test Connection button and then disconnect again.

Hope this helps!

[ashworth]

Good job on fixing it. I have seen a lot of people have this same issue, and they are just stuck.

[Bill_theITguy]

I was pretty much at my wits end . . . no clues whatsoever except for that rPIPTool - NTDLL.DLL error that explains nothing!!!

Dear Blackberry/RIM - please use the standard MSI installer packages with future releases. The rPIPTool MFC installer and transforms used with 4.1.0 is useless if a conflict occurs.

[conwawj]

I had this same problem upgrading from 4.0sp3hf4 to 4.1. To correct this I had to reinstall the 4.0 code then run the 4.1 install.

[sgm-co]

Now I to am having this issues. D click the exe and get nothing but this Rpiptool error.

Any other thoughts?

[dege13]

Anybody have a screenshot or app log message?

[ashworth]

There is no screen shot. When I have seen this problem I got the following in the applicaiton log:

Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 6/29/2006
Time: 10:55:56 AM
User: N/A
Computer: CNOHRLOAD2
Description:
Faulting application Setup.exe, version 1.0.0.1, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x0001f582.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 53 65 74 ure Set
0018: 75 70 2e 65 78 65 20 31 up.exe 1
0020: 2e 30 2e 30 2e 31 20 69 .0.0.1 i
0028: 6e 20 6e 74 64 6c 6c 2e n ntdll.
0030: 64 6c 6c 20 35 2e 32 2e dll 5.2.
0038: 33 37 39 30 2e 31 38 33 3790.183
0040: 30 20 61 74 20 6f 66 66 0 at off
0048: 73 65 74 20 30 30 30 31 set 0001
0050: 66 35 38 32 f582

I just build a new server and it worked. I think it was a Windows thingy.

[noname]

ntdll.dll is a module that contains NT system functions... I would make sure that all software e.g. anti-virus + other watch dogs + monitoring software etc... [many apps use this DLL.... BES also ]... are quited before running the installer... sometimes there are conflicts with other programs...

[NSK]

Hi,
I had the same nightmare but found a fix:

I used several ip-addresses on the server-nic and reduced them to only one(!) ip-address. The update runns without any error and you can add the other ips after finishing the setup.

Cheers,
Chris

[ivanmor]

Anyone that gets this message, shoudl check out the second IP bit, worked for ME!! RIM said to reinstall the OS!


Thanks y'all!

[edonin]

Originally Posted by conwawj

I had this same problem upgrading from 4.0sp3hf4 to 4.1. To correct this I had to reinstall the 4.0 code then run the 4.1 install.

The same "install the old 4.0" code worked for me, too.

Once I got the 4.1SP2 package to run, I also ran into an issue towards the end of the installation where the install program claimed not to have permissions to write files to c:\Program Files\Common Files\Research In Motion\AppLoader.

The folder permissions were all fine. The only way I could get around that one was to drag each preexisting file out of the folder each time the installer complained about permissions, at which point it merrily wrote the file to the very same folder that it claimed not to have permissions to do so.

I've never had a dull production BES upgrade, only the test box upgrades go smooth as silk.

[Kommers]

Couldn't upgrade from 3.x to 4.x, setup.exe wouldn't load. Was told it could be multihomed server problem, but it wasn't it because I had only one NIC.

I managed to resolve this problem the very simple way: first, I updated my
3.x server with the latest service pack (I think it was 7 or something like that), then restarted server and ran setup again. This time setup appeared and the upgrade went on flawlessly.