Bugzilla – Bug 10866
SqueezeCenter 7.3 does not Start on Windows Vista with Norman Security Suite
Last modified: 2009-10-19 02:38:46 UTC
Ticket # 090122-004145 & 090119-001269 http://forums.slimdevices.com/showthread.php?t=57725 Windows XP Windows Vista SqueezeCenter 7.3.x (any) Norman Security Suite **Please note that Norman works with SqueezeCenter 7.2.1** Symptom: After updating from SqueezeCenter 7.2.1 to 7.3.x (any)on a computer running Norman Anti-virus or Security Suite, SqueezeCenter will not start. When trying to get a server log file, the customer(s) get the following error from XP or Vista: ******************************************************************** ": The following CPAN modules were found but cannot work with SqueezeCenter: NET::DNS (loaded 0.63, need 0.63) To fix this problem you have several options: 1. Install the latest version of the module(s) using SPAN: sudo cpan Some::Module 2. Update the module's package using apt-get, yum, etc. 3. Run the .tar.gz version of SqueezeCenter which includes all required CPAN modules. Undefined subroutin &main::man called att slimserver.pl line 89" ******************************************************************** Troubleshooting Steps Taken: -Clean Install of 7.3.1, 7.3.2, 7.3.3, 7.3.4 -Configured Norman Anti-virus to ignore *.my* (to avoid scanning issue) -Configured Norman to ignore whole SqueezeCenter Directory -Configured Firewall to allow 1. Port number: 3483 (TCP) - Name: Server Control 2. Port number: 3483 (UDP) - Name: ServerDiscovery 3. Port Number: 9000 (TCP) - Name: Server Web 4. Port Number: 9092 (TCP) - Name: SlimServer MySQL squeezecenter.exe scanner.exe Although, I did not try allowing ServiceEnabler.exe -Had Switch Start up Options Workaround: Uninstall Norman, and it works fine. ****** I have run this by several people, and they have advised that if it worked before, and now it doesn't, something must have changed, and could now be a bug. I am aware that we generally would not create a bug for Anti-virus or Firewall software.
FYI - 2 more customers with the same issue. 090118-000564 & 090109-000816 Per Dan and James yestderay, I am currently trying to start a communication with Norman, to see if we can come to a resolution Thanks, LaRon
I have another customer experiencing this as well. Right Now ticket # 090210-004971
Created attachment 4800 [details] Norman dstartup Log
Received information from Norman Support. They advised to try turning off On-Access Scanning and the Norman Firewall, to see if it would resolve the issue. It did not. I also have tried adding *.pm to the exclude lists for the On Demand Scanner and On Access Scanner, and still ran into the same issue. (I saw some things in the log file that prompted me to try this) Spoke with Matt Wise last night, and we were able to get a start-up debug log from SqueezeCenter by running the following command: SqueezeCenter.exe --debug server --logfile=c:\SqueezeCenter.log -d_startup 1 I have attached this log. Per Matt Wise, the problem may be that the Norman Security Software is using the same version of CPAN that SqueezeCenter does, and SqueezeCenter could be picking up their version, or, Norman's version of CPAN is overwriting or corrupting our version. Can someone take a look at the attached log file, to see if there is anything else we can try? Thanks, LaRon
Support is dealing with approx. 6 customers suffering this issue in the last 10 days or so. We need to determine if this is something we can fix or not. The interaction of SC with Norman means SC simply will not run. This only happens with 7.3.x and later. 7.2.1 runs smoothly with Norman. cc'ing Andy per software meeting, plus QA.
I installed Norman on a Vista machine, installed SC 7.3.2 - all working and fine. When asked I told Norman to be an "unexperienced" user or something. It then asked me whether I wanted to allow SC as a service a few times. I accepted all of them. And it's all up and running. There must be more to this than "Norman and SC 7.3.x don't work together". What exact Norman version are these users using? What exact SC builds? Any messages during install/first startup?
I spoke too soon: updated to the latest 7.3.3. Now it's failing with the message posted in the original description. Getting closer: if Norman is running, SC can't extract some of the DLLs to its temporary location: Can't write 'C:\Users\abc\AppData\Local\Temp\pdk-abc-2460/35b7d0081cb4404f7cd6bd1437a4f96b/WinError.dll': at perlsvc line 692. (the message about Net::DNS is a red herring) So most likely Norman is considering some files malware, thus blocking access to them, even when the on access scanner is disabled. After uninstalling Norman everything's fine. I've opened a ticket with Norman. We'll see.
Ok, I might have a solution. But it will require a lot of testing on various Windows versions. I'm still uploading the test build, but it should be there in 30 minutes (8pm CET, 11am PST): http://www.herger.net/slim/SqueezeCenter-7.4-25127.exe Please download and install on a Windows machine with Norman AV installed. This version should at least _start_ SC, providing web UI etc. The scanner probably still is broken (didn't apply the workaround to it yet). So don't worry if scanning fails. But if you all could confirm SC does start, that would be of great help. Thanks everybody! (still 25MB to upload...)
change 25138 (7.3.3) change 25139 (7.4) Use --dyndll compile option for PerlApp and friends. This should work around the Norman issue where the AV would block writing out the Perl DLLs. LaRon - please have your customer test the latest 7.3.3 release. Thanks!
Sent email to the customers having the problems to try latest SC version 7.3.3. 090118-000564 090119-001269 090122-004145 Will let you know if this works once I hear back from the customers. Thanks, LaRon
(In reply to comment #10) I had the above problem with v. 7.3.2. but the latest SC version 7.3.3. seems to have fixed it. No problem intsalling or using SC anymore, it all works, thx.
> No problem intsalling or using SC anymore, it all works, thx. Great to here, thanks!
Hello All, 2 of 3 customers states that the issue is resolved. Thanks for your continued help! 090119-001269 090122-004145 LaRon
Tried it today and 7.3.3 works fine with Norman Security Suite. Seems to be solved, it does feel better to have an active anti-virus on a PC running XP. Thanks!
I'm very sorry to say, that we have to revert the change which fixed this issue for you. Please see the following posting for more details: http://forums.slimdevices.com/showthread.php?p=412456#post412456 We're working with ActiveState to find a solution for this issue asap. Thanks for your understanding. Support: please keep tonight's build in a safe place in case customers were calling after the official release.
don't go beyond rev. 25853 - I've reverted the fix for this issue
For those who want a running system without disabling Norman: The official 7.3.2 release is still available: http://downloads.slimdevices.com/SqueezeCenter_v7.3.2/ Dan/support: where's the working 7.3.3 build?
We're working to find a home for it now.
http://www.slimdevices.com/SqueezeCenter-7.3.3_norman.exe would that work?
> http://www.slimdevices.com/SqueezeCenter-7.3.3_norman.exe > > would that work? I'd put it somewhere in the download section. And it should have the revision number in the name, so it's clear what it is.
Having a link from /downloads just like Beta/Nigthly builds do now would work. Something to the effect of "" Windows XP Norman Anti Virus users please click here to download a special build of SqueezeCenter "" WARNING Winodws 2000 users please do not use this version "" Just my 2 centavos
Download page will not link to Norman build per Sam Feng. The thought being it's more confusing than anything (and breaks Win2K) especially with ambiguous "Norman" vs. "Norton" name.
Matt - I'm a bit confused. This issue isn't resolved at all. No normal build would run with Norman installed.
awaiting fixed PDK from ActiveState
*** Bug 14332 has been marked as a duplicate of this bug. ***
Looks as if the --dyndll trick didn't work any more. Support/QA - have you ever tried to "officially" contact Norman to get this issue handled? This is turning into a major pita.
QA has not contacted Norman
Created attachment 6130 [details] settings to get SBS running with Norman Ok, Norman at least is aware of the SBS issue. I only needed to mention Logitech to the first agent I got on the phone. Obviously developers are working on it, but haven't found a solution yet. But to my surprise he knew a workaround: SBS is not blocked by the AV scanner or the firewall (ok, this needs to be configured too, but that's "normal"), but by the "Internet Protection". There's no configuration available for this component, but it can only be enabled/disabled. The component in theory is responsible for scanning mails (according to that agent). Don't know why it would lock out SBS even when _all_ Norman services are stopped. Workaround: disable the checkbox in Install and Updates/Configuration/Products/Internet Protection (see screenshot).
I'd consider this "works for me" now.