VB6 projects not installing on NT4

[gavinpollock]

Hi,

I've created a VB6 project that I'm trying to install on a live Exchange server running NT4.

It uses the scripting.filesystemobject and various other objects, but the installer (creating through the wizard) wants to update the scripting dll (scrrun.dll) and re-start the server. It has version 3.3, and the latest is 5.xxxx . That was the initial problem, and we managed to have it rebooted, but I don't think it overwrote the dll because now the project crashes when it is trying to create an fso object.

Does anyone know any ways to get around these issues. Would doing the project in VB5 help (I really want to avoid that!)? Otherwise what about manually updating the sccrun dll without restarting the machine.

Any ideas would be helpful....!
Cheers
Gavin

[Joacim Andersson]

Put the newer version in an other folder then the old one. Unregister the old version and register the new one.

[plenderj]

I would strongly adise against installing applications onto a server running Exchange. It can be an absolute ***** to get working if you break it.

[Joacim Andersson]

Well register a new version of the scripting runtime wouldn't be any problems. I've done it my self on servers running Exchange.

[plenderj]

Yeah but if something goes wrong it's gonna be a nightmare to fix ... unless he's got a recent backup.

The only thing I ever do on servers running Exchange is go into the Exchange Administrator to make the POP3 Connector check for mail. I leave them well alone otherwise

[gavinpollock]

problem is that it has to run on the Exchange box. It's a mail scheduler thats reading off a database on the network and then using CDONTS to create the mails on the actual box, to cut out on the intranet network traffic.

[plenderj]

Me.FeelUneasy = True