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

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

233.0. "PW Log Internal Parsing Error" by VMSNET::DEFIANT::s_vore (Smile, Mickey's watching! [email protected]) Wed Apr 16 1997 09:19

Note 7254 in pwdoswinv5 talks about this same problem, but w/PW95. 
Now the same customer is now having this exact same problem with 
PW32.  I suspect that one of his servers is returning something odd. 

The short story is that every now & then he'll get an alert box saying
                PATHWORKS Event Logger
                Internal Parsing Error

                        OK ?


Looking at the contents of his log file, I see some characters that 
just don't look right:

0008C0  54 30 30 30 33 4E 3A 09 4C 69 63 65 6E 73 65 20  T0003N:?License
0008D0  22 44 45 43 2D 50 57 58 58 57 49 4E 41 54 30 37  "DEC-PWXXWINAT07
0008E0  2E 30 30 22 20 70 72 65 73 65 6E 74 65 64 20 74  .00" presented t
0008F0  6F 20 73 65 72 76 65 72 20 22 55 4C 20 20 20 20  o server "UL
000900  0D 20 20 20 20 20 20 20 20 09 4C 4F 47 30 30 30  ?        ?LOG000
000910  34 4E 3A 09 53 74 6F 70 20 6C 6F 67 67 69 6E 67  4N:?Stop logging
000920  20 61 74 20 20 30 38 3A 34 34 3A 31 38 2C 20 6F   at  08:44:18, o
000930  6E 20 57 65 64 6E 65 73 64 61 79 20 41 70 72 69  n Wednesday Apri
000940  6C 20 31 36 2C 20 31 39 39 37 0D 0A              l 16, 1997??

note the 4th/5th line - the server name "UL..." looked pretty flummoxed 
to me!

-Steven
T.RTitleUserPersonal
Name		DateLines
233.1VMSNET::DEFIANT::s_voreSmile, Mickey's watching! [email protected]Thu Apr 17 1997 08:428
also, the servers really involved here are RHYTHM and ULMO. ULMO is 
running UNIX V4.0A and PW6 (Advanced Server for UNIX Systems Version 
3.51), where it is both the PDC and (a) licence server.

Both of the servers have "garbage" in their respective "license 
presented to" entries.
233.2VMSNET::DEFIANT::s_voreSmile, Mickey's watching! [email protected]Fri Apr 18 1997 09:1062
here's what the server says it's claimed as NetBIOS names:

Over NetBEUI

ulmo su> nbemon -i 1 -n
         0 Loops Remaining      Fri Apr 18 11:03:04 1997

---Names Configured ( 64)      Display Max ( 64)-----------
    st  lsn sessq dgq  hash  type            Name
 0. 05  -1  80    -1    -1     0   PermName: AA 00 04 00 1B 24
 1. 04   0  -1    -1    -1     0   "PWRK$LULMO      "
 2. 04  -1  -1     2    -1     1   "PWRK$LS        G"
 3. 04   3 192    -1    -1     0   "ULMO            "
 4. 04  -1   4     8    -1     0   "ULMO_0070700     "
 5. 04  -1  -1     5    -1     0   "ULMO           00"
 6. 04  -1  -1     6    -1     1   "SANDQ.DOM      00"
 7. 04  -1  -1     7    -1     1   "SANDQ.DOM      1c"
 8. 04  -1  -1     9    -1     0   "ULMO_0078900     "
 9. 04  -1  -1    10    -1     1   "SANDQ.DOM      1e"
10. 04  -1  -1    11     8     0   "ULMO_0080000     "
11. 04  -1  -1    12    -1     0   "ULMO_0079400     "
12. 04  -1  -1    13     6     0   "SANDQ.DOM      1b"
13. 04  -1  -1    14    -1     0   "SANDQ.DOM      1d"
14. 04  -1  -1    17    -1     1   "0102__MSBROWSE__0201"
15. 04  -1 205    -1    11     0   "PWRK$LULMO     C"
16. 04  -1 189    -1     3     0   "ULMO_00794000000000000"


Over TCP/IP

ulmo su> knbmon -i 1 -n
         0 Loops Remaining      Fri Apr 18 11:07:05 1997

----Names Configured ( 64) Display Max ( 64) NBNSAVAIL=Y--
    st  lsn sessq dgq  hash  type reg clm            Name
 0. 05  -1  -1    -1    -1     0   0   0   PermName: 08 00 2B BC C3 E0
 1. 04   2  -1    -1    -1     0   1   2   "PWRK$LULMO      "
 2. 04  -1  -1     4    -1     1   1   2   "PWRK$LS        G"
 3. 04   5  43    -1    -1     0   1   2   "ULMO            "
 4. 04  -1   6    10    -1     0   0   0   "ULMO_0070700     "
 5. 04  -1  -1     7    -1     0   1   2   "ULMO           00"
 6. 04  -1  -1     8    -1     1   1   2   "SANDQ.DOM      00"
 7. 04  -1  -1     9    -1     1   1   2   "SANDQ.DOM      1c"
 8. 04  -1  -1    13    -1     0   1   2   "ULMO_0078900     "
 9. 04  -1  -1    14    -1     1   1   2   "SANDQ.DOM      1e"
10. 04  -1  -1    20     8     0   1   2   "ULMO_0080000     "
11. 04  -1  -1    21    -1     0   1   2   "ULMO_0079400     "
12. 04  -1  -1    22     6     0   1   2   "SANDQ.DOM      1b"
13. 04  -1  -1    23    -1     0   1   2   "SANDQ.DOM      1d"
14. 04  -1  -1    26    -1     1   1   2   "0102__MSBROWSE__0201"
15. 04  -1 182    -1    11     0   0   0   "PWRK$LULMO     C"
ulmo su>
-------------------------end of screen capture---------------------


ULMO is the name of the server. SANDQ.DOM is the name of the domain.


Does anyone have any idea?
Does anyone (except the customer) care? :-)
233.3JAMIN::WASSERJohn A. WasserFri Apr 18 1997 11:2534
> here's what the server says it's claimed as NetBIOS names:

	Unfortunately the name used might not remain permanently
	registered.  It may be created for this one use and then
	removed.

	Many of these names seem to be of unconventional format.
	By convention, a NetBIOS name should be the base machine 
	name padded with blanks to 15 characters and having an 
	arbitrary byte for the 16th character. Most of the names 
	fit the conventional pattern or fit the conventional
	pattern with an printable prefix but some of the 
	others appear to have embeded nonprintable characters:

 4. 04  -1   4     8    -1     0   "ULMO_0070700     "
 8. 04  -1  -1     9    -1     0   "ULMO_0078900     "
10. 04  -1  -1    11     8     0   "ULMO_0080000     "
11. 04  -1  -1    12    -1     0   "ULMO_0079400     "
14. 04  -1  -1    17    -1     1   "0102__MSBROWSE__0201"
16. 04  -1 189    -1     3     0   "ULMO_00794000000000000"

	If the server is using one of these strange names
	when talking to the License Transponder on the
	client then the client will pass the data on to
	the Event Logger which then gets confused.

	The server were changed to use a name of the 
	conventional form.

	The License Transponder should be changed to
	convert the bad characters to printable text
	before passing the name to the Event Logger.

	Please escalate both problems.
233.4JAMIN::WASSERJohn A. WasserFri Apr 18 1997 11:2816
>	The server were changed to use a name of the 
>	conventional form.
>
>	The License Transponder should be changed to
>	convert the bad characters to printable text
>	before passing the name to the Event Logger.
>
>	Please escalate both problems.


	And another one: The Event Logger should be changed so that
	it does not die with a PARSE ERROR on any message that
	does not end in <CR><LF>.  If it wants to have <CR><LF>
	at the end of every line it should put them there.

	Please escalate that one, too.
233.5HPAQ40YKMVMSNET::DEFIANT::s_voreSmile, Mickey&#039;s watching! [email protected]Fri Apr 18 1997 14:354
> escalate...

done.