Jump to content
Division-M Community
Sign in to follow this  
Barnstable

Not Able To Communicate With Server

Recommended Posts

Hi all

 

I have been running DB successfully for approaching a year now and been very happy with it up until this point:

 

After restart this morning, Drive Bender is now failing to initialise.

 

When running the Drive Bender client, I am presented with an error stating 'An error has occurred while communicating with the server' - see error1.png attached.

 

After clicking OK, the client claims that it is connected to localhost (correct) but states 'There was an error getting the license details Activate'. When trying to activate using my license key , it states invalid key (I assume because this has previously been activated, or cannot communicate with the server).

 

See error2.png - When running the Drive Bender Manager, my server appears under Pool instances but gets stuck at 'Pool(s) starting up...'. There is also an info message stating 'There was an error getting the license details. Active license'. Under this, a warning message states 'Restart Drive Bender'. When doing this restart, the same scenario occurs as above.

 

When clicking 'Maintenance and repair', I get the error 'An Error has occured while communicating with the server' (also see error2.png).

 

A possible cause could be Windows updates that were installed on the restart (see installedupdates.png). These were:

 

KB2504637
KB3176937
KB3176935

 

I have tried removing these installed updates and restarting to no success however.

 

All drives that were participating in the drive pool are still visible in Device Manager.

 

Please could anyone help me resolve this issue? As you can probably tell, my knowledge of/experience with DB is very limited. If any further details are required, please do let me know. I have files on the pooled drives that I will need immediate access to.

 

Thanks very much.

post-4684-0-30828800-1474543265_thumb.png

post-4684-0-58301300-1474543265_thumb.png

post-4684-0-86112200-1474543265_thumb.png

Share this post


Link to post
Share on other sites

I have now managed to resolve this issue by performing a full reinstall of Drive Bender.

 

During this process, I found that I could not uninstall Drive Bender - the uninstaller complained that it could not perform the action.

 

For reference if anyone else encounters this error, I resolved this by reinstalling .NET framework 3.5. The issue was that the uninstaller was trying to reference a missing file, regasm.exe in c:\windows\microsoft.net\Framework\v2.0.50727\.

 

This thread can be closed.

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...