Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I have Systemworks 2006, since Jan 2007, but after having to re-install it it'll work for a while and then after an update and restart it suddenly says I've -1 days on my subscription which doesn't come due until jan 2009.
I've tried the SymKBFix download, and I can't even tell if it has installed itself properly.
But the really interesting thing is I have another system Hard Drive with this Systemworks installed, and it is up-to-date and working!
Has anybody else had this problem, and if so how did you solve it?
P.S. My O.S. is Win2000 SP4.
Thankyou, but I am already in contact with them.
I just thought I'd check with other users through the forum in case they could suggest something helpful.
Oh, and how do you go about starting one of these Chat Sessions?
I hadn't come across them before.
Just to bring it up to date, I have re-installed NSW206 to see if I can replicate the problem.
First, SymKBFix seems to have installed properly this time, though I'm not too sure.
Second before I could get to the point when the original error occured I had another error saying I had made too many installations for the product key.
The Incident# is: 080717-005249.
My system is:
Windows 2000 Professional Service Pack 4, with
Norton Systemworks 2006, on
AMD Athlon™ XP 2000+ Processor
ASRock K7S8XE Motherboard
1,834,480KB RAM
NVIDIA GeForce 7300 GT Graphics Card
Maxtor 6L080L0 (80GB) Hard Drive
I have a second Hard drive, Fujitsu MPG3204AT E(20GB) with
Windows 2000 Professional Service Pack 4, upgraded from Windows 98.
Our Customer Support team can reset that install count for you, that can be resolved easily by contacting the support team. Thanks!
I ended up initiating a 'Chat Session' to deal with that problem.
The engineer fixed it, and my original problem revealed itself.
Eventually an Analyst was called in to deal with it.
The problem is still unresolved. All they ended up doing was telling me this was an issue with NSW 2006 and Win2000 (which sounds like I'm not the only one with this problem), and then offering to install NSW 2005.
I even offered to help them as I have a working version of 2006 on the other hard disk, and I'd come across discrepancies between the two versions.
Usually differences found were in the 'Version' numbers of DLL's and EXE's in the Symantec Shared folder on each disk.
I'm now searching all the Symantec files, those that I can find, and cataloguing these inconsistent files and will pass on the results to Symantec.
I have refused NSW 2005 as I'm sticking to my rights under UK law. Though I am currently expecting a resolution which is satisfactory to both myself and Symantec.
I've checked through the folders installed by Norton and I've found these discrepancies between the Working and Erroneous copies:
Program File\Common Files\Symantec Shared
For the Working copy of NSW 2006 files:
LNKCOM.DLL version: 199.1.19.308
MDSCAN.DLL version: 199.1.19.308
RSCAN.DLL version: 199.7.22.308
SymPrRec.dll version: 199.1.19.308
For the Erroneous copy of NSW 2006 files all files above were of version 19.0.0.48
S32RASU.DLL
Working copy version is 1998.5.15.305, whilst the Erroneous copy had version 1998.3.6.304.
Program File\Common Files\Symantec Shared\CCPD-LC
File symlcrst.dll of the Working copy was version 1.9.1.762, whilst the Erroneous copy file had no version number.
Program File\Common Files\Symantec Shared\SPBBC
BbRGen.dll version: 2.0.0.73
SPBBCDrv.sys version: 2.4.0.1
SPBBCEvt.dll version: 2.0.0.73
SPBBCSvc.exe version: 2.0.0.73
In the Erroneous copy were the above files, in the Working copy all were of version 2.1.0.4
And UpdMgr.exe was 2.4.0.1 in the Erroneous copy, but was 2.2.0.8 in the Working copy.
Program File\Norton Systemworks\Norton Utilities
The Working copy has S32DMAPL.DLL version: 28.0.0.181 , whilst the Erroneous copy has version: 19.0.0.48.
Program File\Symantec\LiveUpdate
The Erroneous copy has a 1.Settings.Default file, the Working copy doesn’t.
And I've found an inconsistency in the System32 folder of the O.S.
The Working copy has apitrap.dll, but it isn’t present on the hard drive for the Erroneous copy.
Can someone explain these inconsistencies?
Would they have a bearing on the problem I'm having to deal with?
I've found that there are more files on the Working copy's HDD that missing from the Erroneous copy's HDD.
System32 folder of the O.S.
s32lucp1.dll
And from the System32\config folder
symlcbrd.sys
That's a discrepancy of 16 files! Of which 3 are missing from the copy with the problem!?!
I somehow don't think that is right!!!
Anyway, now for the Good News.
NSW 2006 is working.
I don't know what happened, but while I was running my file comparison the Activation window popped up.
I ran it, and it reported that I had 147 days left on my subscription. Shortly after NSW started running properly.
Like I said, I don't know what happened, but it is possible activated something from the other NSW which bypassed the problem.
But that is only a supposition.
It might be a good idea to contact our Customer Support team to help with this issue:
http://www.symantec.com/norton/support/selectproduct_ts.jsp
If you start a Chat Session, they can access your system to troubleshoot this issue directly on your system. Thanks!