Error connecting to server. Access is denied.

ShadowProtect 3.3 was working OK. I even did one full C drive restore. Then I downloaded 3.4 and started the install. The install got about 80%(?) through and froze — solid! I rebooted, unstalled, then ran Registry 1st Aid. I rebooted again, then reinstalled the 3.3. (I've done this procedure more than once but without the 3.4 part.)

Each time, when I reopen ShadowProtect, I get the following error: ... Error connecting to server. Access is denied. ... The License is disconnected.

Product activation is greyed out and only Explore Backup is working. I'm running XP Pro SP3, Asus Striker Extreme, Q6600, Velociraptor C drive. — I'm not afraid of regedit, but I need really detailed instructions if someone wants me to go there.

Comments

whyisntitworking

Re: Error connecting to server. Access is denied.

I have had the same problem, i'm not sure the exact reason it occurs but here was the solution I found.

Select View Network

Highlight localhost

Select Connect.

 Hopefully this will fix your problem

NotTooBright

Re: Error connecting to server. Access is denied.

[quote user="whyisntitworking"]

I have had the same problem, i'm not sure the exact reason it occurs but here was the solution I found.

Select View Network

Highlight localhost

Select Connect.

 Hopefully this will fix your problem

[/quote]

Thank you for your suggestion, but that didn't work.

Can you think of something else. Although I have all my data backed up via SmartSync to external storage, my C Drive has several applications on it that are not on my .iso, I would hate to have to restore (again).

STC-JWT

Re: Error connecting to server. Access is denied.

 First,

 You will want to install v3.4 If the install fails. let us know, we want to know why.

 After installing 3.4 you will need to do the following:

click on “Network Views” under the “Views” panel on the left, it will pull up the network views on the right. You should see a unmanaged node. If there is a red ‘x’ next to the icon you are disconnected from the shadow protect service. Simply click on the unmanaged Node and then click Connect.

 If it continues to fail. Please click on the request help link at the top of the support center and fill out the support form.

__________________

I am no longer in the technical support department at StorageCraft Technology Corporation. If you need immediate assistance with an issue you are experiencing, please fill out a technical support request from the link below http://forum.storagecraft.com/Community/web2case/

NotTooBright

Re: Error connecting to server. Access is denied.

[quote user="JWT"]

 First,

 You will want to install v3.4 If the install fails. let us know, we want to know why.

 After installing 3.4 you will need to do the following:

click on “Network Views” under the “Views” panel on the left, it will pull up the network views on the right. You should see a unmanaged node. If there is a red ‘x’ next to the icon you are disconnected from the shadow protect service. Simply click on the unmanaged Node and then click Connect.

 If it continues to fail. Please click on the request help link at the top of the support center and fill out the support form.

[/quote]

Where can I find v3.4 on your website? When the 3.4 install failed a couple of days ago, I deleted the downloaded file —— and 3.3 cannot connect to find a new version.

NotTooBright

Re: Error connecting to server. Access is denied.

Success — finally.

I used the 3.3 disc to restore a June image to the C: drive. The restoration went perfectly and that image had an active 3.3 on it. But I still wanted 3.4, right! So I uninstalled the 3.3 and tried again to install 3.4, for which a forum post had given me a link. Pfffttt!

3.4 froze about 90-95% through the install. I let it "sit" for an hour (way too long for a Q6600 in an Asus Striker Extreme mb!). Then I gave up and rebooted. The 3.4 showed up as an ACTIVE application in Start>Programs, but it would not go farther than the Explore, so I was back to square 1. However, the 3.4 did NOT appear in ADD/REMOVE programs! So I couldn't uninstall it and go back to 3.3.

From forum links I was able to download the v3.4 .iso. I burned the .iso to a CD, then used the CD to install OVER the interrupted 3.4 install. That was a success.

FTTester

Re: Error connecting to server. Access is denied.

There is definitely some other application that is blocking the correct install and/or setup of ShadowProtect. It is often best to temporarily disconnect from the internet, shutdown and security products/registry "cleaners" etc, install ShadowProtect and then reboot. Check ShadowProtect performs a good backup and then restart the security apps and reconnect to the internet. If ShadowProtect fails in some way after that, you normally have to tweak the security product to allow ShadowProtect, and its components, to run.

Have you used msconfig, or services.msc, to 'reconfigure' the services run at start up and the service start-up types? It might be an idea to make sure you have not stopped one of the dependent services.

Just out of interest. do you have any log files from the various times you have run Registry 1st Aid? Something showing what stuff it removed or changed in the registry?

 

 

NotTooBright

Re: Error connecting to server. Access is denied.

Sorry FT,

No logs, but I did use Iolo System Mechanic to shut down some "unnecessary services at startup. Should this happen again, I'll try installing w/o the internet connection and with all security shutdown.

FTTester

Re: Error connecting to server. Access is denied.

I've written a couple of posts listing the services that you need to have running with ShadowProtect. It might be worth checking the services. You need to make sure they are running correctly and the start-up type is correct. If you look in the registry you will also see that there are entries that ShadowProtect depends on, that are not listed simply as ShadowProtect. For instance, some are also listed under names like ShadowStor (the old company name). It would not surprise me if a badly written registry "cleaner" decided to clean things up by deleting some of these entries. At the very least, try and keep a log of the registry changes. At least that way you can troubleshoot a problem when a subsequent installation fails or application stops working.

Post back if you have any issue with a re-install.