2015-03-11 12:36 AM - edited 2015-12-18 01:05 AM
Exploring the Shares possibilities in OnCommand we turned off cifs on an interface in order to force shares through a specific subnet, using CLI to our netapp host: options interface.blocked.cifs (interface name)
After doing this we had problems backing up an SQL database, the server lost connection to disks and started asking for a valid certificate. Enabling the cifs interface again with options interface.blocked.cifs “” brought back the disks, but a problem still remains. The SnapDrive and SnapDrive Manager services stopped working.
How can we activate the services again so we can start backing up our SQL Databases again. We have tried the registry change for prolonging the shut down time for services to start. Still no result. We have tried rebooting. Reinstalling is not an option.
Any help in this matter is greatly appreciated.
This is our products in relation to the error.
Snapmanager for sql server 184.108.40.2061
Sql version 2008 r2
Server OS 2008 r2
Snapdrive manegement version 7.0.3
Solved! SEE THE SOLUTION
2015-03-11 03:43 AM
Could you please provide further information, for example: What is the error message you are recieving when the service fails to start? What are the snapdrive event ID's in your servers application event log?
This KB might be of interest to you:
Have you logged a support case?
2015-03-11 08:04 AM
These are the two error messeges when trying to start SnapDrive service and the manager services service:
Windows could not start the SnapDrive service on Local Computer. Error 1067: The process terminated unexpectedly.
Windows could not start the SnapManager Service services on Local Computer. Error 1068: The dependency service or group failed to start.
Event log give me this:
Faulting application name: SWSvc.exe
.NET Runtime version 2.0.50727.5485 - Fatal Execution Engine Error (000007FEF941600A) (80131506)tion Engine Error (000007FEF941600A) (80131506)
Thank you for the link, I have tried the explorer settings with no result. I can't change the XML files, but that would be interesting to try since one of them is mentioned above. (SWSVC.exe) This might be due to insufficient admin right to change it.
I have a support case on this, awaiting answer.
2015-03-11 03:46 PM
This might be of interest:
If that's no related to your servers configuration then see this KB:
this describes how to debug a windows service using windbg:
2015-03-19 07:53 AM
After changing the IE options, prolonging the service time before closure-registry-hack and updating the .NET framework we finally reinstalled the snapdrive and snapdrive for SQL-server manager and it worked again. If not restarting the server works, try reinstalling the application, right?
Anyway, thanks for the input. If anyone else is struggeling with the services not starting, reinstalling the application might be a last way out.