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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

1091.0. "JBC-E-INVMSG error startting OA$FORMATTER" by KAOFS::D_STREET () Tue Jul 21 1992 17:37

    Hello,
     I have a customer who has installed VMS5.5-1, and is running ALL-IN-1
    V2.4 (patch level K603) with WORDPERFECT under ALL-IN-1. After
    relinking, copying the modified files, and rebooting, they get the
    following error when trying to start the OA$FORMATTER queue.
    
    	JBC-E-INVMSG - invalid message recieved.
    
     The logical SMBSRVSHR has been mentioned in other places as a possible
    cause if it is defined, in this case it is not defined. However another
    logical SMBSRVSHR_WPCORP_PTR51 equates to SMBSRVSHR (in the system
    table). 
    
    				Are there any ideas?
    
    					Derek Street

T.R	Title	User	Personal Name	Date	Lines
1091.1	Did OA$FORMATTER link without errors?	IOSG::HALLC	Chris Tostevin-Hall	`Tue Jul 21 1992 18:17`	8
	Just guessing but... If the SMBSRVSHR logical was defined when they did the ALL-IN-1 relink then OA$FORMATTER.EXE will not have linked cleanly. My guess is they're trying to use this image. Cheers, Chris.
1091.2	relink clean, SMBSRVSHR defined to be SYS$SHARE:SMBSHARE	KAOFS::D_STREET		`Wed Jul 22 1992 18:06`	9
	Hello, The client has a copy of their relink, and displays no errors. However the instructions for integrating WORDPERFECT into ALL-IN-1 state that the logical SMBSRVSHR must be defined to be SYS$SHARE:SMBSHARE. The client has OA$FORMATTER dump files available if this would be of assistance. Derek Street
1091.3	Right version of OA$FORMATTER.EXE being used?	IOSG::HALLC	Chris Tostevin-Hall	`Wed Jul 22 1992 18:33`	12
	Cluching at straws now.... The OA$FORMATTER.EXE that was successfully linked was copied to :- SYS$COMMON:{SYSEXE} I suppose? Is there a bad version in SYS$SYSROOT:[SYSEXE] ? I'm pretty sure you will have already been checked but I'm just checking. Cheers, Chris.