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

Conference abbott::mailworks-vms

Title:	MailWorks for OpenVMS
Notice:	kit info notes 3-6; policies note 2; reporting bugs note 7
Moderator:	KOALA::LAVASH

Created:	Wed Jul 28 1993
Last Modified:	Mon Jun 02 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1583
Total number of notes:	6814

1537.0. "A1MAIL$CONNECT and MUAS$SERVER crash..." by MLNCSC::ZAGHI () Thu Feb 06 1997 03:22

Hi,

Referring to the note 1519 (The problem was that the process A1MAIL$CONNECT 
randomly crashed).

The customer upgraded MailWorks for OpenVMS from version 1.2-ECO5 to version 
1.3a but the process A1MAIL$CONNECT still crashes . Moreover the situation
seems to be worse than before the upgrade , in fact now MUAS$SERVER crashes 
too . 
The new software configuration is the following....

SERVER:

DECmailworks 1.3a
MESSAGE ROUTER 3.3
PATHWORKS 4.2-1
UCX 3.2
OPENVMS 5.5-2

CLIENTS :

TEAMLINKS V2.0 On the following platforms...
WINDOWS 3.1 , WFW , WINDOWS 95 , WINDOWS-NT

Transport between server and clients are both DECNET and TCP/IP .

The following files are available on the node TIPTAP :

1)
(MUAS$SERVER dump file and DMW$COLLECT_INFO run after the crash)

SYS$SPECIFIC:[FAL$SERVER.AGIP.crash_muas]

DMW$COLLECT_INFO_AMBRA2.SAV;3
MUAS$SERVER.DMP;3

2)
(A1MAIL$CONNECT dump file and DMW$COLLECT_INFO run after the crash)

SYS$SPECIFIC:[FAL$SERVER.AGIP.CRASH_A1CONNECT]

A1MAIL$CONNECT.DMP;1
DMW$COLLECT_INFO_AMBRA2.SAV;1


Could anyone give me any tips ?

Many thanks in advance 

Regards 

Paolo (CSC , Milan)

T.R	Title	User	Personal Name	Date	Lines
1537.1	TIPTAP: 46.906; tiptap.mln.dec.com 16.192.32.41	NETRIX::"[email protected]"	Augusto Dal Porto	`Thu Feb 06 1997 03:43`	1
	[Posted by WWW Notes gateway]
1537.2	Upgrade EVERYTHING!!!	IOSG::REESA	Arfon Rees (REO2 F/L9 DTN: 830 6028)	`Thu Feb 06 1997 04:20`	24
	Paolo, I haven't looked at the dump information provided but I'm immediately drawn to the versions you state: >DECmailworks 1.3a >MESSAGE ROUTER 3.3 >PATHWORKS 4.2-1 >UCX 3.2 >OPENVMS 5.5-2 >TEAMLINKS V2.0 On the following platforms... Mailworks should be 1.3A plus ECO3 plus ICF35. UCX and Pathworks versions look quite old? TeamLinks should be no less than V2.5 ECO4 You must upgrade before anyone can do anything. The versions you state are old and have known critical problems. Regards Arfon.
1537.3	re. to 2	MLNCSC::ZAGHI		`Fri Feb 07 1997 04:25`	26
	Hi Arfon , >>UCX and Pathworks versions look quite old? >>TeamLinks should be no less than V2.5 ECO4 The customer upgraded his products at the minimum versions that the manual "MailWorks for OpenVMS Installation V1.3a" chapter 1.1 reports . The only product that this chapter doesn't report is TEAMLINKS . Could I see reported in any document the minimum version of TEAMLINKS supported by MailWorks 1.3a ? We are talking about a very big and critical customer (petrol company : AGIP) that has hundreds PCs with TEAMLINKS installed ... so they want to read some ufficial document that reports the minimum TEAMLINKS version supported . >>Mailworks should be 1.3A plus ECO3 plus ICF35. I've just sent to the customer ECO3 kit . Where could I found ICF35 ? Many thanks for your cooperation and for your patience Regards Paolo (CSC , Milan)
1537.4	Release notes state 'latest version'	KOALA::LAVASH		`Mon Feb 10 1997 07:48`	44
	Paola, > >>UCX and Pathworks versions look quite old? > >>TeamLinks should be no less than V2.5 ECO4 > > The customer upgraded his products at the minimum versions that the manual > "MailWorks for OpenVMS Installation V1.3a" chapter 1.1 reports . > The only product that this chapter doesn't report is TEAMLINKS . > Could I see reported in any document the minimum version of TEAMLINKS > supported by MailWorks 1.3a ? > We are talking about a very big and critical customer (petrol company : AGIP) > that has hundreds PCs with TEAMLINKS installed ... so they want to read some > ufficial document that reports the minimum TEAMLINKS version supported . MailWorks for OpenVMS V1.3A shipped over 2 years ago. In that time ECOs and new versions other products have shipped. These new releases are not documented because they were not available at the time that V1.3A shipped. In that 2 year period, many improvements in the various products have been made. Two years ago, the products listed in the SPD were the minumum version of the products at that time. Today, Engineering has solved many critical problems. It is highly recommended that the customer move to the lastest technology. Anything older that the latest technology may contain known critical problems. The closest offical documentation that I am aware of is in the release notes for MailWorks for OpenVMS V1.3A-3: Modifications have been made to fix memory leaks in the Connect Server when using the TeamLinks for Windows client. The fix for these memory leaks required modifications to both the Connect Server and the TeamLinks for Windows client. To install the fixes, you must upgrade the MailWorks for OpenVMS to the current version. Then, install the latest patches that are available for TeamLinks for Windows. The memory leaks will still occur if the patches are not installed. The release notes do not explicitly name a specific version of TeamLinks because a critical problem could be fixed in a version released after MailWorks is released. I hope this helps, -diana
1537.5	where is ICF35 patch	MLNCSC::ZAGHI		`Wed Feb 12 1997 10:09`	14
	Hi Diana , Thanks for the explanation . The last question is : -Where could I found ICF35 patch ? (This is the patch mentioned in reply 2 ) Many thanks too Regards Paolo (CSC , Milan)
1537.6	Will mail you patch	GRITS::CARTER_A		`Wed Feb 12 1997 14:21`	11
	Hi, I will assume that your customer is running 1.3A-3 on a VAX and will mail you the patch. Please keep in mind that the patch can only be installed on V1.3A-3. Regards, Angela Stover Mailworks Support
1537.7	reply to 6	MLNCSC::ZAGHI		`Fri Feb 14 1997 04:35`	12
	Hi Angela , thanks for your reply and to have sent to me the patch . I'd like to ask you two last questions : What kind of patch is ICF35 ? Is it an official patch ? Many thanks too Paolo (CSC , Milan)
1537.8	ICF35 is an official patch	UTRTSC::SCHOLLAERT	Ajax: World Champions 1995	`Fri Feb 14 1997 07:41`	8
	Hello Paolo, Angela might be asleep. I can confirm ICF35 is an official patch submitted by MailWorks Engineering. Cheers, Jan
1537.9	Yes, its official	GRITS::CARTER_A		`Mon Feb 17 1997 17:18`	13
	Hi, I was asleep and enjoying a day of vacation. The read me file discusses everything that the patch fixes and yes it is official. When your A1MAIL$CONNECT process hangs does it go into a MUTEX wait state. I find that many times there is a problem with bytlm or page file quota on the A1MAIL$CONNECT process. These params can be adjusted in the file A1MAIL$CONNECT_STARTUP.COM. Regards, Angela
1537.10		TAGEIN::SCHOEN		`Thu Feb 20 1997 08:13`	15
	Hi Angela, please can you send me also the ICF35 patch ? A customer of mine has also a problem with the A1MAIL$CONNECT process (crash with access violation). My customer use DMW 1.3a-3. thanks Thomas (MCS - Frankfurt)