Title: | Microsoft Exchange Server |
Notice: | |
Moderator: | FLASK2::SYSTEM |
Created: | Fri Feb 17 1995 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Thu Jun 05 1997 |
Number of topics: | 1099 |
Total number of notes: | 5174 |
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
808.1 | XMERVU::imladris.ilo.dec.com::grainne | Fri Jan 10 1997 15:20 | 11 | ||
808.2 | I had to DELETE the file | DEVIN::LUCAS | Are we having fun yet? | Mon Jan 13 1997 17:01 | 7 |
808.3 | Can't open RICHED32.DLL on NT Alpha | NNTPD::"[email protected]" | Kent Meagher | Mon Apr 28 1997 23:59 | 25 |
Re: -1 I'm entering this reply in hopes that it will help someone else. I was pulling down the Alpha Exchange client from the CCS server, and was getting 78% of the way done when Setup complained that it could not open RICHED32.DLL. Sure, the file was there, but it was apparently being used by some process and SETUP could not open the file. Well, I had nothing else running, only DIAL-UP (which I obviously needed). I could not delete the file either, since it was opened and would not grant me access. Guess what it was? You might have gotten it, it was FX!32. You have to go into Control Panel, Add/Delete Applications, choose FX!32, and click on the Disable radio button, then reboot. (Don't Remove it, just Disable). After this, I tried deleting the DLL file as a test, and was allowed to. That gave me a good feeling. So I came up without FX!32, dialed in, and was able to sucessfully install Exchange Client for Alpha. Then of course, when I was done, I got back into Control Panel and Enabled FX!32, booted again, and was fine. Hope this helps! [Posted by WWW Notes gateway] | |||||
808.4 | But don't delete RICHED32.DLL! | NNTPD::"[email protected]" | Kent Meagher | Tue Apr 29 1997 00:02 | 8 |
re -.1 After reading my last reply, I didn't mean to imply that you should delete RICHED32.DLL. You'll need it for the Exchange install. I undeleted it after my test ;>). Buena suerte! [Posted by WWW Notes gateway] | |||||
808.5 | Just rename | pcivb1.vbo.dec.com::BERGER | Vincent Berger | Tue Apr 29 1997 22:23 | 9 |
Generally when something like that happens, you can just rename the file that can't be accessed (you can't delete it but you can usually rename it). That will allow SETUP to proceed happily. Of course if the file is really a new version, you might need to reboot to have the new file taken in account, but in general it's the same stuff being installed over and over again (MSVCRT.DLL and MFC*.DLL are good at that). Vincent | |||||
808.6 | fx!32 and not being able to delete the file | NETCAD::BARENYS | John Barenys | Wed Apr 30 1997 03:22 | 15 |
re .3 After a successful install of the Exchange Client for Alpha with FX!32 running I read over your note a few times to see what the difference could have been. It appears that the DLL the client wanted to install over was in use by FX!32 (most likely the optimizer got a hold of it). I would guess that this is something that happened as a result of the original failed install. If you have the time you might want to try it again w/ FX!32 installed and see if fails again. The folks at the FX!32 development team might like the data point... -John |