GeekyDaddy Posted August 27, 2019 Report Share Posted August 27, 2019 When I try to update the I get a persistent error. I have rebooted, uninstalled and re-installed. I have ensure my Win10 machine is up to date. I have three machines where Immunet is installed, and all three report the same issue. Link to comment Share on other sites More sharing options...
ritchie58 Posted August 27, 2019 Report Share Posted August 27, 2019 A 503 error indicates that the server is not available at that moment. This typically occurs if the server is undergoing maintenance or is simply too busy to handle your request. I would suggest you wait a day or so and then attempt another update if the server is actually undergoing maintenance. Also, what build of Immunet are you currently using? To find out simply mouse over "About" located in lower right-hand corner of the UI. Let us know if you continue to encounter this error code. Regards, Ritchie... Link to comment Share on other sites More sharing options...
zombunny2 Posted August 30, 2019 Report Share Posted August 30, 2019 Hello - For some reason the forums won't let me sign in to my account - but this is user zombunny. Just a quick note to say I have been having this exact same issue for at least 2 days, on Win10 Pro 64-bit with a fresh install of Immunet 6.5.0.11255 (no quarantine or settings data whatsoever backed-up from the previous installation). I also notice that the Immunet home page (but not the IPTray client) says "0 users protected from 0 threats" - I wonder if this is related? Link to comment Share on other sites More sharing options...
ritchie58 Posted September 1, 2019 Report Share Posted September 1, 2019 Are you still encountering that 503 error code now zombunny? If so that's something that will need to be further investigated if this continues with some users. Personally I'm not seeing this behavior but I'm using Win 7 so it makes me wonder if it's a possible bug with Win 10 users only. Link to comment Share on other sites More sharing options...
zombunny2 Posted September 2, 2019 Report Share Posted September 2, 2019 Hello Ritchie, yes still having the same issue. I get the exact same error message, but the ClamAV databases still update as if there's no problem. I also still get cloud detections when I scan my malware archive. I think this issue is simply related to Immunet checking for a new Immunet version. Cloud detection and database updates seem to be unaffected. 1 Link to comment Share on other sites More sharing options...
ritchie58 Posted September 3, 2019 Report Share Posted September 3, 2019 Yes, you are correct there zombunny. That's the portion of the updater that looks for new builds to download & install so this error is not jeopardizing the protection Immunet provides you. Still, it's a nuance to users that should be corrected as soon as possible in my view. Thanks much for your update on the issue. Link to comment Share on other sites More sharing options...
zombunny2 Posted September 4, 2019 Report Share Posted September 4, 2019 I have sent a support dump on this issue. I initially thought it might be caused by my custom hosts file, but I have ruled this out (I restored the stock Windows hosts file, rebooted, and the problem persists). Another unusual feature of my installation is that I regularly stop the Immunet services, copy assorted custom databases into the ClamAV folder, then restart Immunet. I doubt this would cause issue (it hasn't in the past), but may make it difficult to interpet the logfiles! Link to comment Share on other sites More sharing options...
cajuncup Posted September 4, 2019 Report Share Posted September 4, 2019 Two days ago my Windows 10 got a serious update (took about 3 hours). Since that time I've been getting that 503 error. Coincidence? 1 Link to comment Share on other sites More sharing options...
ritchie58 Posted September 5, 2019 Report Share Posted September 5, 2019 Mmm. Another Win 10 user encountering this 503 error. There is definitely a developing pattern going on here since no other Immunet user that has Win 7, 8, 8.1 or supported Server platforms has reported this. I'm going to send the admin Rob. Turner a PM regarding this issue for you guys to see if he can look into this for you. Link to comment Share on other sites More sharing options...
zombunny2 Posted September 5, 2019 Report Share Posted September 5, 2019 I am already in discussion with Rob as he had spotted this thread Nothing odd was found in my log files, which leads me to conclude a recent Windows update has broken something yet again. It's getting that ridiculous, I've actually ditched all my Windows installations apart from one, which I need for a single piece of technical software. I also even use GNU/Linux at work nowadays unless I have to reboot to use a specific proprietary tool. The AV is managed at work, but I've noticed that out of all the machines, it only ever tends to break on the Win10 ones, and even then it's only after an update. Coincidence? I think not! Link to comment Share on other sites More sharing options...
ritchie58 Posted September 5, 2019 Report Share Posted September 5, 2019 Thanks for letting me know that you & Rob are in contact. Just wanted to make sure he was aware of the situation by the PM I sent. I hope you're allowing security patches to be installed. That's important for any supported Microsoft platform. If it is some sort of conflict with a Win 10 update it certainly won't be the first one we've encountered. That's the reason I have yet to upgrade to Win 10 from 7. I'm waiting for the end of Microsoft's support for Win 7, at the end of this year, for the simple reason that I'm hoping most of the serious bugs with 10 have already been rectified. Link to comment Share on other sites More sharing options...
Rob.T Posted September 6, 2019 Report Share Posted September 6, 2019 Hi all, I am indeed working on debugging this. A quick trouble shooting test for anyone on the thread have update issues is to try to browse to each of the url's below. They should all show something in a browser window or prompt you to download and save an executable. Don't bother saving or installing them, Immunet will get do that automatically for you if needed. This step just proves Immunet will be able to connect to all the resources it might need. 1)https://mgmt.consumer.amp.cisco.com/health/ 2) update.immunet.com/updates/protect/update-6.5.0-64.xml 3) https://sourcefire-apps.s3.amazonaws.com/fireAMP/windows/6.5.0.11255/Release-Logging/installer-univ-tcp-injected-ExprevDisabled.exe 4) https://orbital-88fcda36-e81e-9b43-6085-5f5d6054dc22.s3.us-west-2.amazonaws.com/consumer-ampwin-setup-0.9.3.exe Link to comment Share on other sites More sharing options...
cajuncup Posted September 7, 2019 Report Share Posted September 7, 2019 Trouble shoot complete, Link to comment Share on other sites More sharing options...
zombunny2 Posted September 9, 2019 Report Share Posted September 9, 2019 @Rob.Turner I can confirm that I can either see text or get a download prompt for every one of those links supplied. @ritchie58 Don't worry, I of course still allow Windows updates on my internet-connected machine. I have Pro so am fortunately able to defer any non-security updates for up to a year, which I recommend everyone should do before their PC gets bricked. It gives Microsoft a good chance at fixing the worst of their problems before their "improvements" reach your machine - unless the next broken update they release without testing just happens to be a security one... As a side note, When your Windows 7 reaches end-of-life, one option would be to just have a dual-boot scenario: Switch to GNU/Linux for anything that requires the internet, and keep your unsupported Win7 installation as-is, unpatched, for any obscure software you might still need to run occasionally, but can't get on GNU/Linux. You'd just need to keep the Windows 7 installation offline, for instance by disabling your network interfaces in the device-manager, or unplugging your network cables. I'm aware there's a learning-curve, it's a matter of personal taste, and It's not possible for everyone, but I'm about 90% of the way there. I used to dual-boot and value both OSs for their respective qualities, but I'm rapidly getting to the point where I just need to get the work done and Windows now gets in the way of that for me. 1 Link to comment Share on other sites More sharing options...
ritchie58 Posted September 10, 2019 Report Share Posted September 10, 2019 Thanks for your advice zombunny. That would be an interesting option to use a duel-boot configuration. I didn't even think of that. I know I do have a few dated software programs that I still like to use but would definitely be incompatible with Win 10. Even if I deleted a bunch of stuff I still wouldn't have enough free disk space on my current C:\ drive to create a partition and install another OS but I could buy an additional hard drive and just switch my mobo's BIOS first boot device setting when I want to still use Win 7 . I'll definitely give that some thought dude! Glad to hear you are allowing security updates to take place. I was worried for your system's security if you were not allowing those. Link to comment Share on other sites More sharing options...
Aris Posted October 2, 2019 Report Share Posted October 2, 2019 this error is still there. So is there any solution? Hello from Greece Link to comment Share on other sites More sharing options...
ritchie58 Posted October 3, 2019 Report Share Posted October 3, 2019 Hi Aris, There is a new build available. Have you updated to the new 7.0 version yet? https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe We haven't (so far) received any reports of this 503 error with the new build unless you already updated. Regards, Ritchie... Link to comment Share on other sites More sharing options...
Aris Posted October 3, 2019 Report Share Posted October 3, 2019 yes. I have already updated and its still there. On a win7 pc there is no problem, same router-ip Link to comment Share on other sites More sharing options...
ritchie58 Posted October 4, 2019 Report Share Posted October 4, 2019 Ok, this is something the devs will definetly need to look into ASAP. Link to comment Share on other sites More sharing options...
zombunny2 Posted October 4, 2019 Report Share Posted October 4, 2019 Hi all! This is just a quick note to say that I completely removed Immunet, purged all its configuration files and quarantine, manually checked the hard disk for leftovers etc. - and then restarted the computer. I then did a completely fresh install of Immunet 7. I now no longer have the "Error 503" problem. I'd recommend those still having problems to try this, as long as it's not too much trouble for them to do it. Before you do so, make sure nothing valuable is sitting in your quarantine, and make a little note of all the scan-exclusions you added in the settings! I do wonder if the last Immunet in the 6.x series might have corrupted a configuration file somewhere. It might be that this bug has disappeared in version 7.0, and that users just need to refresh their installation. Link to comment Share on other sites More sharing options...
nirmeshptl Posted October 4, 2019 Report Share Posted October 4, 2019 On 8/30/2019 at 9:30 AM, zombunny2 said: Hello - For some reason the forums won't let me sign in to my account - but this is user zombunny. Just a quick note to say I have been having this exact same issue for at least 2 days, on Win10 Pro 64-bit with a fresh install of Immunet 6.5.0.11255 (no quarantine or settings data whatsoever backed-up from the previous installation). I also notice that the Immunet home page (but not the IPTray client) says "0 users protected from 0 threats" - I wonder if this is related? Hey @zombunny2 Sorry to heart that you are facing this issue. I need info to dig more into this. Are you still seeing this issue while trying to upgrade to 7.0.0 Gather Full Support dump and send it over to us What was your upgrade path: Old 6.x.x -> 6.5.0? Link to comment Share on other sites More sharing options...
nirmeshptl Posted October 4, 2019 Report Share Posted October 4, 2019 On 8/27/2019 at 4:57 AM, GeekyDaddy said: When I try to update the I get a persistent error. I have rebooted, uninstalled and re-installed. I have ensure my Win10 machine is up to date. I have three machines where Immunet is installed, and all three report the same issue. @GeekyDaddy Sorry to heart that you are facing this issue. I need info to dig more into this. Are you still seeing this issue while trying to upgrade to 7.0.0 Gather Full Support dump and send it over to us What was your upgrade path: Old 6.x.x -> 6.5.0? Link to comment Share on other sites More sharing options...
zombunny2 Posted October 8, 2019 Report Share Posted October 8, 2019 On 10/4/2019 at 5:56 PM, nirmeshptl said: Hey @zombunny2 Sorry to heart that you are facing this issue. I need info to dig more into this. Are you still seeing this issue while trying to upgrade to 7.0.0 Gather Full Support dump and send it over to us What was your upgrade path: Old 6.x.x -> 6.5.0? Hello @nirmeshptl please see my post that is immediately above the one I quote here. It answers all of your questions. Thank you for your interest, but I no longer have the issue with 7.0.0. Link to comment Share on other sites More sharing options...
Aris Posted October 9, 2019 Report Share Posted October 9, 2019 Big trouble. Tried to uninstall version 7 to see if a clean install corrects the problem. Unfortunately, i couldn't for some reason to complete uninstall, tried a lot of times. So i stopped some services and deleted files, almost everything in immunet and orbital directories. Did some registry cleaner runs with ccleaner. Services are gone. It still finds version 7 is installed and doesn't proceed with install. Only a dll file in scriptid folder exists but i don't know which process or service is loaded and i can't delete it. I believe that is the problem. Any suggestions? Link to comment Share on other sites More sharing options...
Aris Posted October 9, 2019 Report Share Posted October 9, 2019 the file that i cannot delete is damsicom64.dll Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now