[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:	WinNT-Clusters
Notice:	Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:	DECWET::CAPPELLOF

Created:	Thu Oct 19 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	863
Total number of notes:	3478

680.0. "ClusterAdministrator crashing after VC++ installed" by DECALP::KLAVINS (Ed Klavins, RTR Engineering) Wed Mar 12 1997 08:30

Run into a problem with running ClusterAdmin. All of a sudden, I cannot
start the tool anymore. The message displayed is "instruction at 0x004464d8
referenced memory at 0x00147510. The memory cannot be written".

I strongly suspect this is because I recently installed VC++ 4.2 (on
Alphaserver 1000) -- I can't think of anything else I could've changed in
the environment to cause this. Since VC is installed, I can actually go
into the debugger and see where it is crashing:

_AFX_TERM_APP_STATE::_AFX_TERM_APP_STATE()
	=> which tried to call AfxInitialize(FAALSE, _MFC_VER)
$E321() line 71 + 20 bytes
MSVCRT! 0024ebfc()
wWinMainCRTStartup + 248 bytes

Searching for AfxInitialize in VC documentation, I come up with nothing.
Did this call become obsolete ? Anyone have any ideas how I can get arond
this? (uninstall VC++ is an option I suppose; any other ideas?)

Fortunately, it seems as if the cluster 'functionality' is still there.
I.e. services fail over, etc.

This was running V1.0 SP1 on NT 3.5 SP5. My first idea was to upgrade to
V1.0 SP2, in the hope that it would get fixed thru upgrading. But the same
thing still happens after upgrading.

Thanks, ed

T.R	Title	User	Personal Name	Date	Lines
680.1		LJSRV1::BOURQUARD	Deb Walz Bourquard	`Wed Mar 12 1997 11:26`	7
	Maybe copy the older VC++ 4.1 DLLs into the same directory where NTCLUSTER.EXE is?? (Assuming that you have access to the older DLLs, of course.) I'm guessing that a newer DLL was installed into the winnt\system32 directory and I believe that the image first looks for DLLs in its own working directory.
680.2		DECALP::KLAVINS	Ed Klavins, RTR Engineering	`Thu Mar 13 1997 01:48`	11
	> Maybe copy the older VC++ 4.1 DLLs into the same directory > where NTCLUSTER.EXE is?? (Assuming that you have access > to the older DLLs, of course.) > Good idea. [I had tried uninstalling VC without success, since it doesn't uninstall the updated MSVC.DLL in WINNT35\SYSTEM32]. Which leads to the next question... Wish I had the old DLLs (apparently, uses MFC40U.DLL and MSVCRT40.DLL) Anyone got an Alpha handy with NT clusters installed and prepared to ZIP up, say, MFC.* and MSVC. from SYSTEM32? ed
680.3		DECALP::KLAVINS	Ed Klavins, RTR Engineering	`Thu Mar 13 1997 10:20`	8
	Thank goodness for backups. Managed to find a tape with a VC4.1 installation from another machine. After copying MFC40.DLL, MFC40U.DLL and MSVCRT40.DLL into the NTCLUSTER.EXE directory, it works again.... This should be something of interest to the developers, I should imagine? Is there anyone to whom I should be sending this info? ed
680.4		LJSRV1::BOURQUARD	Deb Walz Bourquard	`Thu Mar 13 1997 10:34`	6
	> This should be something of interest to the developers, I should > imagine? Is there anyone to whom I should be sending this info? It is. You already did. (I'm a developer for the Cluster Administrator :-)