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.
See also my thread on this subject http://community.norton.com/norton/board/message?board.id=Norton_360&thread.id=505
Really appreciate the reply mel.
360 Version 2.2.0.2
Windows XP
Home Edition 2002
Service Pack 2
Had NIS 2007 previously. Downloaded 360 from the store, so probably on top.
Error: "LU1812" even after running the Hotfix tool
This solution requires that you use Internet Explorer. If this page is open in any other Web browser, open it in Internet Explorer.
If the hotfix is not available, wait two weeks and then run the tool once again.
Results of LUALL.... 1812 Error.... then....
Submit A BugYou are using Symantec software and have encountered an error. Please assist Symantec by submitting your information.
Ended up at
Welcome to SupportLet us help solve your issue.
Been there. Not in the mood to do it again. Had 2 out of 5 techs disconnect from me without warning because they could not figure it out (imo).
Intelligent updater seems to work.
Log...
Mon Jun 02 18:55:28 2008 : ******************************************************************
Mon Jun 02 18:55:28 2008 : Starting Intelligent Updater - Version 5.0.25
Mon Jun 02 18:55:28 2008 : ******************************************************************
Mon Jun 02 18:55:28 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:55:28 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:55:28 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:55:28 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:55:28 2008 : IU RES SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the iuResource.dll
Mon Jun 02 18:55:28 2008 : IU RES LOAD: Successfully loaded the resource file..
Mon Jun 02 18:55:28 2008 : IU MODE: IU is running is FULL mode.
Mon Jun 02 18:55:33 2008 : CONFIG LOAD SUCCESS: Successfully loaded the configuration file: iuConfig.xml.
Mon Jun 02 18:55:33 2008 : IU INFO: File-name : 20080602-024-v5i32.EXE
Mon Jun 02 18:55:33 2008 : IU INFO: Creation-date : 20080602
Mon Jun 02 18:55:33 2008 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Mon Jun 02 18:55:33 2008 : Entry details:
Mon Jun 02 18:55:33 2008 : Update-File: VIRSCAN.zip
Mon Jun 02 18:55:33 2008 : Update-Desc: Virus Definitions
Mon Jun 02 18:55:33 2008 : Auth DLL Name: SAVIUAuth
Mon Jun 02 18:55:33 2008 : Auth DLL Location: local
Mon Jun 02 18:55:33 2008 : Auth Content-Type: virus definitions x32
Mon Jun 02 18:55:33 2008 : Deploy Content-Type: virus definitions x32
Mon Jun 02 18:55:33 2008 : Deplo DLL Name: SAVIUDeploy
Mon Jun 02 18:55:33 2008 : Deploy DLL Location: local
Mon Jun 02 18:55:33 2008 : AUTH DLL LOCATION: IU will read the DLL location from registry - SAVIUAuth
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:55:33 2008 : REG FAILURE: Failed while reading the value for key named
Mon Jun 02 18:55:33 2008 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SAVIUDeploy
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:55:33 2008 : REG FAILURE: Failed while reading the value for key named
Mon Jun 02 18:55:33 2008 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Mon Jun 02 18:55:33 2008 : IU failed while deploying V because a compatible product could not be found on the system. Please make sure that a compatible Symantec product is installed on the system.
Mon Jun 02 18:55:33 2008 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Mon Jun 02 18:55:33 2008 : Entry details:
Mon Jun 02 18:55:33 2008 : Update-File: VIRSCAN.zip
Mon Jun 02 18:55:33 2008 : Update-Desc: Virus Definitions
Mon Jun 02 18:55:33 2008 : Auth DLL Name: ISAuthDLL
Mon Jun 02 18:55:33 2008 : Auth DLL Location: local
Mon Jun 02 18:55:33 2008 : Auth Content-Type: virus definitions x32
Mon Jun 02 18:55:33 2008 : Deploy Content-Type: virus definitions x32
Mon Jun 02 18:55:33 2008 : Deplo DLL Name: ISDeployDLL
Mon Jun 02 18:55:33 2008 : Deploy DLL Location: local
Mon Jun 02 18:55:33 2008 : AUTH DLL LOCATION: IU will read the DLL location from registry - ISAuthDLL
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while fetching the path for DLL : C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:55:33 2008 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - ISDeployDLL
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:55:33 2008 : REG SUCCESS: Success while fetching the path for DLL : C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:55:33 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:55:33 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:55:33 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:55:33 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:55:33 2008 : AUTH SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the authorization dll C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:55:33 2008 : AUTH LOAD SUCCESS: Successfully loaded the authorization dll - C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:55:34 2008 : DEPLOY SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the deployment dll C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:55:34 2008 : DEPLOY LOAD SUCCESS: Successfully loaded the deployment dll - C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:55:34 2008 : AUTHORIZATION SUCCESSFUL: VIRSCAN.zip is successfully authorized for deployment.
Mon Jun 02 18:55:34 2008 : DEPLOY PATH SUCCESS: VIRSCAN.zip will be deployed at location C:\PROGRA~1\COMMON~1\Symantec Shared\VirusDefs\tmp74fa.tmp
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:55:34 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:55:34 2008 : UNRAR LOAD SUCCESS: Successfully loaded the UNRAR DLL.
Mon Jun 02 18:55:34 2008 : UNRAR OPEN SUCCESS: Success opening RAR file VIRSCAN.zip
Mon Jun 02 18:55:37 2008 : UNRAR EXTRACT SUCCESS: Succesfully extracted VIRSCAN.zip to C:\PROGRA~1\COMMON~1\Symantec Shared\VirusDefs\tmp74fa.tmp
Mon Jun 02 18:55:38 2008 : POST PROCESS SUCCESS: Successfully performed post processing for VIRSCAN.zip
Mon Jun 02 18:56:12 2008 : ******************************************************************
Mon Jun 02 18:56:12 2008 : Starting Intelligent Updater - Version 5.0.25
Mon Jun 02 18:56:12 2008 : ******************************************************************
Mon Jun 02 18:56:12 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:56:12 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:56:12 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:56:12 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:56:12 2008 : IU RES SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the iuResource.dll
Mon Jun 02 18:56:12 2008 : IU RES LOAD: Successfully loaded the resource file..
Mon Jun 02 18:56:12 2008 : IU MODE: IU is running is FULL mode.
Mon Jun 02 18:56:18 2008 : CONFIG LOAD SUCCESS: Successfully loaded the configuration file: iuConfig.xml.
Mon Jun 02 18:56:18 2008 : IU INFO: File-name : 20080602-024-v5i32.EXE
Mon Jun 02 18:56:19 2008 : IU INFO: Creation-date : 20080602
Mon Jun 02 18:56:19 2008 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Mon Jun 02 18:56:19 2008 : Entry details:
Mon Jun 02 18:56:19 2008 : Update-File: VIRSCAN.zip
Mon Jun 02 18:56:19 2008 : Update-Desc: Virus Definitions
Mon Jun 02 18:56:19 2008 : Auth DLL Name: SAVIUAuth
Mon Jun 02 18:56:19 2008 : Auth DLL Location: local
Mon Jun 02 18:56:19 2008 : Auth Content-Type: virus definitions x32
Mon Jun 02 18:56:19 2008 : Deploy Content-Type: virus definitions x32
Mon Jun 02 18:56:19 2008 : Deplo DLL Name: SAVIUDeploy
Mon Jun 02 18:56:19 2008 : Deploy DLL Location: local
Mon Jun 02 18:56:19 2008 : AUTH DLL LOCATION: IU will read the DLL location from registry - SAVIUAuth
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:56:19 2008 : REG FAILURE: Failed while reading the value for key named
Mon Jun 02 18:56:19 2008 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SAVIUDeploy
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:56:19 2008 : REG FAILURE: Failed while reading the value for key named
Mon Jun 02 18:56:19 2008 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Mon Jun 02 18:56:19 2008 : IU failed while deploying V because a compatible product could not be found on the system. Please make sure that a compatible Symantec product is installed on the system.
Mon Jun 02 18:56:19 2008 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Mon Jun 02 18:56:19 2008 : Entry details:
Mon Jun 02 18:56:19 2008 : Update-File: VIRSCAN.zip
Mon Jun 02 18:56:19 2008 : Update-Desc: Virus Definitions
Mon Jun 02 18:56:19 2008 : Auth DLL Name: ISAuthDLL
Mon Jun 02 18:56:19 2008 : Auth DLL Location: local
Mon Jun 02 18:56:19 2008 : Auth Content-Type: virus definitions x32
Mon Jun 02 18:56:19 2008 : Deploy Content-Type: virus definitions x32
Mon Jun 02 18:56:19 2008 : Deplo DLL Name: ISDeployDLL
Mon Jun 02 18:56:19 2008 : Deploy DLL Location: local
Mon Jun 02 18:56:19 2008 : AUTH DLL LOCATION: IU will read the DLL location from registry - ISAuthDLL
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while fetching the path for DLL : C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:56:19 2008 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - ISDeployDLL
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while opening key
Mon Jun 02 18:56:19 2008 : REG SUCCESS: Success while fetching the path for DLL : C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the authorization dll C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:56:19 2008 : AUTH LOAD SUCCESS: Successfully loaded the authorization dll - C:\Program Files\Norton 360\tpIUAMgr.dll
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:56:19 2008 : DEPLOY SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the deployment dll C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:56:19 2008 : DEPLOY LOAD SUCCESS: Successfully loaded the deployment dll - C:\Program Files\Norton 360\DefUDply.dll
Mon Jun 02 18:56:19 2008 : AUTHORIZATION SUCCESSFUL: VIRSCAN.zip is successfully authorized for deployment.
Mon Jun 02 18:56:19 2008 : DEPLOY PATH SUCCESS: VIRSCAN.zip will be deployed at location C:\PROGRA~1\COMMON~1\Symantec Shared\VirusDefs\tmp758d.tmp
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED BEGIN: Started.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED CLASS3: Succeeded find the class 3 ID, returning TRUE.
Mon Jun 02 18:56:19 2008 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Mon Jun 02 18:56:19 2008 : UNRAR LOAD SUCCESS: Successfully loaded the UNRAR DLL.
Mon Jun 02 18:56:19 2008 : UNRAR OPEN SUCCESS: Success opening RAR file VIRSCAN.zip
Mon Jun 02 18:56:22 2008 : UNRAR EXTRACT SUCCESS: Succesfully extracted VIRSCAN.zip to C:\PROGRA~1\COMMON~1\Symantec Shared\VirusDefs\tmp758d.tmp
Mon Jun 02 18:56:22 2008 : POST PROCESS SUCCESS: Successfully performed post processing for VIRSCAN.zip
But then I went back to 360 and ran Live Update and got the 1806 Error with instructions to do the luall again.
The technicians removed and reinstalled 360 numerous times. To no avail. I still kept getting an error message.
Then to make matters worse, when I clicked on settings, tasks scheduling, and tried to click on any box, my cpu jumped up to 50% or more, and the window locked up for about a minute. Nothing changed on the box I clicked. To make matters worse, I showed it to a tech on line and he tried to convince me that the cpu activity was normal.
an excerpt...
Sathish: There will not be much difference as you have 1 GB ram.
Sathish: High CPU usage can happen only if you have 512 MB ram.
Mr. : no... it is Norton using the cpu
Mr. : have LOTS of BIG programs that cause me no problems
Sathish: a normal programme only use memory to load.
Sathish: But as a protection programme, it should scan each and every files and then load into memory. Norton 360 is a memory resident antivirus.
Sathish: It will be there in the memory to scan each files loaded into memory.
Mr. : I understand, but why does clicking on a box eat up cpu???
Mr. : NIS didn't do that
Sathish: Norton Internet Security is a lighter programme.
Mr. : not according to the ads
Mr.: it doesn't work
Sathish: Thasts why I said Norton 360, is a high end protection software designed to give you complete protection, especially when you are doing online transactions. It has a two way firewall.
Sathish: Norton 360 is a large programme, it may use lot of system resources, thats why we have included PC Tuneup in Norton 360 in order to ensure that your system is working without high CPU usage.
Mr. earl : would you put up with having to wait after clicking one button???
Mr. earl : that is ridiculous
Sathish: Analyst has closed chat and left the room
I spent my entire day and night yesterday trying to get 360 to work. I do not believe it is meant for my puter for whatever reason. Works fine on the other puter (as far as I know). Should have stayed with NIS or whatever.
Again, appreciate your reply mel,
Cheeta
Is it really the case -- from the transcript you quote -- that you only have 512MB of RAM?
That's on the light side in my experience since XP is happy to use more than that. On my machine with 2GB of RAM (upgraded a while ago from 1GB with VISTA on board also but not running at the same time) it is using just under 700MB and all I'm doing is writing this message.
Additional RAM is usualy an excellent investment, and depending on your PC, need not be expensive these days.
I don't have 512MB of RAM. The technician said something about that. I have no idea what he meant by that statement.
I have an Intel Pentium 4 CPU 3 Mhz
1023 MB of memory
I agree, additional ram is a good investment.
I am going through the same thing on three computers. Exact same download. I have done every solution.
It seems that norton admin has no idea what is going on.
There are now two threads on this problem, perhaps the Moderators could combine them? Better still Symantec could supply a solution or at least acknowledge that there is a problem.
DJJ
cheeta wrote:I don't have 512MB of RAM. The technician said something about that. I have no idea what he meant by that statement.
I have an Intel Pentium 4 CPU 3 Mhz
1023 MB of memory
I agree, additional ram is a good investment.
Glad to hear that -- shows I read the messages <g>
I hope you sort it out soon. I have a great deal of confidence in what Norton are doing here in these Forums.
I have been to support with 6 techs so far. Each one basically does the same thing.
Today Norton was uninstalled in safe mode. Reinstalled. Everything looked fine. But as soon as it was complete, the tech disconnected. That has happened most of the 6 times. And they report the problem as solved.
So I went to manually do live update and got "LiveUpdate was able to install some of the available updates but other updates failed with errors".
Personally, I don't believe there was an update to be had. It was updated when it was reinstalled. But I can't live with something that tells me there is an error. How do I know if there really is an error?
I'm tired and frustrated with this problem. Every time I sign in to get a refund, I get another tech that says he can fix it. They don't understand that it has already been reintalled over 6 times. Some techs tried more than once.
Norton admin probably sees this as a small problem, if they see it at all. What I hope they see is the reviews for their product online. There are a LOT of unhappy folks out there. Doubt that they will.
Greetings,
In one of your posts, you mention that you were directed to the following page:
Results of LUALL.... 1812 Error.... then....
Submit A BugYou are using Symantec software and have encountered an error. Please assist Symantec by submitting your information.
Did you go through the log submission process? If so, we should be able to find the logs on our backend server and have a look at the problem.
I have spent the entire day trying to get support for Live Update on Norton 360. Been through 4 technicians on line to no avail. Have watched 360 be uninstalled and reinstalled numerous times.
Hve use Norton for years. But getting ready to permanently uninstall it.
Any help would be appreciated.
Yes I did send it. I have no reference to it.
Hope it helps you find what is going on. It might solve a lot of folks problems.
This problem appears to have been fixed (at least on my system) . Presumably the program update has been re-released corrected or withdrawn altogether. Either way Live Update now shows all items up-to-date.
Thank you.
DJJ
Derek,
Are you running version 2.3.0.9. now? With me same thing but the update is no longer there so I think the program update to 2.3..0.9 has been withdrawn from lu
Pls check and advise
Grumpster,
You are correct. My version is still showing 2.2.0.2 so they have removed the program update.
DJJ
PS. The above applies to my Vista Home Premium PC, my XP laptop shows 2.3.0.9 but has the 'Network "AT Risk" problem'. You can't win them all!
All of my computers are now running fine. The update has been withdrawn.
I manually ran live update with no problem too.
Not sure who fixed it, but they were obviously aware that a problem existed. Should have been communicated to the users, imo. Good job nevertheless.
Curious what the cause of the problem was. Probably way over my head - lol.
I guess this problem is now solved.
No the problem is not solved. The ones of us who in XP ended up with version 2.3.0.9 are still faced with the red X and the at risk statement .
Grumpster,
I misread your post above.
I know the frustration and can completely relate.
None of the "fixes" that are available right now are going to help. At least that was what my experience was.
Not sure it would help, but try submitting your error log. I was able to do that using luall.
jgreen posted earlier....
"In one of your posts, you mention that you were directed to the following page:
Results of LUALL.... 1812 Error.... then....
Submit A BugYou are using Symantec software and have encountered an error. Please assist Symantec by submitting your information.
Did you go through the log submission process? If so, we should be able to find the logs on our backend server and have a look at the problem. "
Not sure if it can help, but beats the heck out of chatting with online tech support. The employees in this forum at least give an alternative to uninstalling and reinstalling.
Good luck.
[edit: Inserted HR for clarity.]
Hi Gumpster,
Just confirming that the problem you are mentioning here is the one in the Home Networking status detection - is that correct? I'm not sure if you saw my response yesterday in that post:
http://community.norton.com/norton/board/message?board.id=Norton_360&message.id=632
Matt