Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Internal Compression and Time Synchronization Errors

Posted on 1998-09-14
Medium Priority
Last Modified: 2008-03-04

I received the following error msgs on the NetWare 4.11 server console. Could anyone explain on the internal compression error and the "Time synchronization has been lost after 2591 successful polling loops." msgs. Any way to rectify them ? TIA

 8-29-98  12:12:49 am:    SERVER-4.11-2985
   Severity = 3  Locus = 2  Class = 5
   Internal compression error: file 'SOTRAN21.CDX' volume 0 intermediate size 512169. Data encode counts from intermediate file generation (227742) and intermediate file processing (227739) mismatch invalidating intermediate file.

 9-03-98  12:12:10 am:    SERVER-4.11-3284
   Severity = 3  Locus = 2  Class = 5
   Internal compression error: file 'CONTACTI.NDX' volume 0 size 298496 The projected size of the compressed file (86344) did not match the byte size of the compressed file (86348).

 9-05-98  12:38:23 am:    SERVER-4.11-3374
   Severity = 3  Locus = 2  Class = 5
   Internal compression error: file 'CONTACT1.DBF' volume 0 size 2199356.Intermediate file inconsistency at offset E4048h: Value 0h should be 31h or 30h

 9-10-98  12:35:35 am:    SERVER-4.11-3374
   Severity = 3  Locus = 2  Class = 5
   Internal compression error: file 'SOYTRN21.CDX' volume 0 size 4671055.Intermediate file inconsistency at offset 11A04Bh: Value 0h should be 31h or 30h

 9-15-98  10:04:20 am:    TIMESYNC-4.15-72
   Severity = 1  Locus = 17  Class = 19
   Time synchronization has been lost after 2591 successful polling loops.

 9-15-98  10:04:45 am:    TIMESYNC-4.15-138
   Severity = 0  Locus = 17  Class = 19
   Time synchronization has been established.
Question by:danfoo
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Accepted Solution

brosenb0 earned 200 total points
ID: 1593428
To rectify the internal compression error, you should ensure that hardware write caching is disabled on the server's drives.  With Segate and Micropolis drives this is set with a utility program rather than jumpers or switches.  Some other vendors drives automatically detect NetWare as the OS and disable write caching.  Check the procedure with your drives vendor.

If the errors stop after performing the above, your files should be ok.  If not then attempt to copy the files to a workstations drive, delete the original on the server and copy it back.  If this fails then you will have to restore from tape.

The timesync error could be caused by a number of problems.  Some common causes include: -

1) A comms problem exists that is preventing timesync packets reaching their destinations.  This could be an overloaded or failing router port, LAN segment or switch.  It could even be your server's NIC or network cabling.  Check for errors using Monitor. We recently had the same timesync problem on our network.  The reference time server is connected via an ATM network to various Cisco routers which feed all over the place.  The version of Cisco IOS that was running in some of them (the routers operating system) was screwing up the ATM <-> token-ring translation and SAPs where not being broadcast.  Cisco came out and upgraded the IOS and now all is well.  An easy way to tell if you have a SAP broadcast problem is to get hold of the utility SAPMON.EXE (Sapmn12.exe).  You can download it from www.net-utils.com.  Note that if only using configured time sources ie. not using SAP type 0x026B (Time source), SAP type 0x0004 (file server) must still be able to get through.

2) In a multi-tree environment, if using SAP type 0x026B, ensure that all servers have tree mode set to on.  This way they will not accept time from servers in another tree.  Better still, whilst requiring a little more work to setup, only use configured time sources.

3) Depending on your time provider topology, Your reference time server or any of your primary time servers may have an problem.  Sometimes restarting these may help.

4) Some dork may have brought up an NT server or workstation with FPNW or GSNW with the same internal IPX address as one of your servers or segments.  This will result in substantial packet loss.

5) If using locally administered MAC addresses, another dork may have duplicated your servers MAC address somewhere else.  This will be more likely to cause a problem in a SRB token-ring environment, as the servers and workstations send explorer frames to find the route to the destination node and will get indeterminable results.  Whilst this scenario is unlikely, we run a global network with 10s of thousands of users, thousands of servers and many many dorks and I have seen it happen !

Good Luck.


Author Comment

ID: 1593429
Thanks for the detailed info.

Yesterday, went to the reserve server AMIBIOS setup - Advanced CMOS setup to change the "Internal Cache" from Writeback to Disable. And with this change, the "External Cache" was automatically changed from Enable to Disable. This applies only to the PC mainboard cache and not the drive. The PC is a Fujitsu MP5166X-B09E1 model and was not specifically designed for server use; I use it as my reserve server. I will need to check with my vendor or Fujitsu Website or drive manufacturer Website (to be determined by opening up the PC cover) on the HD documentation which was not supplied to me. There were some jumper documentation on the mainboard manual but they do not apply to cache setting on HD.

Your proposed scenario 2, 3. 4 and 5 do not apply in my environment. But there was great info !

I will leave this Qn open for a few more days for comments before I close it. FYI, the latest server console msg shows:

 9-15-98   6:16:40 pm:    TIMESYNC-4.15-138
   Severity = 0  Locus = 17  Class = 19
   Time synchronization has been established.

 9-16-98   4:25:39 am:    SERVER-4.11-3284
   Severity = 3  Locus = 2  Class = 5
   Internal compression error: file 'ICDIST21.CDX' volume 0 size 238080 The projected size of the compressed file (160084) did not match the byte size of the compressed file (160088).


Author Comment

ID: 1593430
I will close this Qn and and repost if there is any other related issue. I will check on the HD spec and configuration after I have finished some other tasks.



Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What monsters are hiding in your child's room? In this article I will share with you a tech horror story that could happen to anyone, along with some tips on how you can prevent it from happening to you.
Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question