[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

2959.0. "INTEGER_CONVERSION error in 3.0 after upgrade" by VNABRW::SCHNABEL () Sat Jul 03 1993 23:45

    Hello!
    
    We installed ALL-IN-1 3.0 german, (upgrade from 2.4), did install the 
    K701 Patch, recompiled, started ALL-IN-1 (on 2 Nodes of the VAXcluster)and entered Wordprocessing.
    I can create drawers, but if I try to create a document, it only
    returns on the bottom of the supposed document this:
    Message number 092FF7A1:integer_conversion
    	           another formatter(?) error number. 
    
    Help would be urgently needed, as we are here working the weekend, to
    have the system running for monday morning.!!!!
    
    THanxx a lot in advance 
    Marianne Schnabel_with_another_exhausted_kollegue_at_my_side 
    
    
T.RTitleUserPersonal
Name
DateLines
2959.1All document types?IOSG::NEWLANDRichard Newland, IOSG, REO2-G/L2Sun Jul 04 1993 21:356
The facility code of the message number (092F) indicates that the error is
coming from WPS-PLUS.  Are you able to create other types of documents,
such as ASCII? 

Richard

2959.2oauser:WPL_INDEX_TABLE.DAT ?UTRTSC::SCHOLLAERTYou name, we support it...Mon Jul 05 1993 12:0915
    Hello Marianne Schnabel_with_another_exhausted_kollegue_at_mour_side,
    
>               -< INTEGER_CONVERSION error in 3.0 after upgrade >-
    
    We have seen this error in the Dutch version in a little bit
    different context. Deleting oauser:WPL_INDEX_TABLE.DAT (WPS-PLUS 3.x 
    paragraph numbering thing) fixed it.
    
    Regards,
    
    Jan
        
    

    
2959.3Some more informationVNOAPP::TIMA_204410Plus en plus seule...Wed Jul 07 1993 17:5178
	THanxx for answering, but as the customer is back on 2.4 I cannot 
    	do as you recommend. So the best thing is, that I provide as much
    	information I have. 

   
    	Environment: 
    	VAXcluster 4 nodes, on 2 nodes ALL-IN-1 started. (2.4 german), 
    	one ALL-IN-1 disk, two user disks, and about 20 shared directories 
    	on another disk.  VMS 5.5-2

    	I worked together with the ALL-IN-1 responsible at the customer site, 
    	since about 5 weeks , we did any Preinstallation requirements, we ought
    	to do and started in the evening the upgrade.Customer had yet shut down
	ALL-IN-1.

    	The installation finished ok, but in the log file I found some errors. 
	 
	1) As I was told, DECwindows was not installed so I went on without
	   full CDA support. In the A1$POSTINSTALL.COM sections when ALL-IN-1
	   is started, the logfile then said:	
	   Installing the CDA images
	%OA-E-NOINSTALL, Error installing the Formlibrary
	-RMS-E-FNF, file not found. 
	I presumed, that was because of the missing CDA RT services of VMS.
	Investigating today I was told, that they have DECwindows, and found 
	some images in SYS$LIBRARY:CDA$ACCESS.EXE and DDIF$VIEWSHR.EXE.!!!
	Could that be the cause of the INTEGER_CONVERSION problems?? 

	2) also in the A1$POST section:
	   %OA-I-LASTLINE,"converting 2.4 PROFIL records for Custom. Mgtm..."
	   %OA-I-LASTLINE,"ALL-IN-1 running -- Converting user profile data file"
	   %OA-I-AIMNOOPEN,File #pstfile cannot be opened. 

	I had a look at the PST_TO_PROF.SCP and PST_TO_PROF2.SCP and think 
	the fields haven't been updated in the profiles. 
        By the way, at any point of the log,the message of "xxxx.flc is 
	obsolete" came out.. (memres.flc, manager....)
 
	3) The IVP passed but the logfile couldn't be found. On the system 
	   existed no IVP account, only MANAGER and POSTMASTER. (?)

So as I presumed there was no serious problem, I continued doing the german 
postinstallation tasks, replacing WPLGETDOCSEL.FRM, WPSDINST.FRM, WP.FRM/WP_WPS-
PLUS.FRM, FC1.FRM, WPL_LANGS.FRM,CXP$HOSTS.FRM, SMPR$INDEX.FRM, WPPARG.FRM, 
WPPARG3.FRM,WPSRWHAT.FRM, NIENTR.FRM, OA$SCT$SDF.FRM,OALLV.OBJ, OAFC$SERVER_
STOP.SCP, FDDTR.FRM, FC$IAD$INDEX$MENU.FRM, OA$LIST$FILES$MENU.FRM, OA$LIST$
MENU$MORE.FRM, new FORMAT.DAT, new STDFORMAT.DAT, new TMSTG__OPTIONS1.MEM
and .RNO, and a new FC.A1$MSG copied to OA$BUILD_GERMAN. 

I did precompile OAFORM, MEMRES, MANAGER, CM but am not sure having compiled 
and installed the message file too... Maybe the next hint. 

Then I shut down ALL-IN-1 again, installed K701 (3.0-1).
Did aftwerwards the relink  ($set def oa$build_share , @a1_eco001030_relink)
> While the relink I got some error messages about duplicate entries in the 
VAXCRTL library, (link-w-muldef...) I found an old 2.4 Sitelink.com and 
commented anything out. > ok. 
Now I wanted to enter ALL-IN-1 with /USER=MANAGER/OVER=SHUT, to do the 
ECO postinstall. but could enter only on one node without problems, on the 
other I got an error message that I cannot open formlibrary !as. 

After another problem with the Systemmanager having started ALL-IN-1 on one 
node without privs, I managed to enter ALL-IN-1 without any problems, BUT
couldn't create a document, read it, edit it, or print it > 

Formatter message number 092FF7A1 and INTEGER_CONVERSION with another message 
number 092F8059. I had a look in the trace and saw the document being created.
So it seems to me that the problem is not being able to handle messages 
internally.

After all these explanations, I hope someone of you has a guess, where I forgot 
something, what indeed becomes more and more obvious for me ...

Thanxx 
Marianne   



2959.4Solved, but don't know (why,what,etc...)VNABRW::EHRLICH_KPennywise, the clown!Mon Jul 19 1993 19:4015
    Hi 
    	on Friday/Saturday Marianne and I were at customers' site doing the
    upgrade once more. Guess, the result is ??????
    
    Bingo, the upgrade was fine! No problems occured on this system. Everything
    was fine. Strange things happen here.
    
    Maybe an old SITELINK23.com - which had a mystery includestatement of 
    a WP*****.OBJ (I don't know exactly, because we've deleted the file and 
    the content is also removed from my brain!!) caused the problems.
    
    But we're happy about a happy customer (now) and a running ALL-IN-1.
    
    Best regards
    Charly_from_CSC_Vienna_or_the_another_exhausted_colleague_at_her_side_!!!