Weird Excel File Session Issue
-
I'm right. Something to do with Backup Exec not mounting the volume correctly on my backup server is shutting off the Virtual Disk Service. So I'm sure the server restarts the service, it works temporarily and then it turns it off again so on and so forth. Interesting problem. I turn off the backup server temporarily to test and it isn't doing that anymore.
-
Process of elimination.
-
Nice find - similar weird problems like my disk issue this morning causing files to have no permissions.
-
@Dashrender said:
Nice find - similar weird problems like my disk issue this morning causing files to have no permissions.
Okay so It was working for a bit and the Virtual Disk Service is still crashing. It also lists this in Event Viewer:
"The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Virtual Disk service, but this action failed with the following error:
An instance of the service is already running."I am also getting a ton of spooler errors I assume due to the service stopping and the drive being unavailable.
-
@wirestyle22 said:
@Dashrender said:
Nice find - similar weird problems like my disk issue this morning causing files to have no permissions.
Okay so It was working for a bit and the Virtual Disk Service is still crashing. It also lists this in Event Viewer:
"The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Virtual Disk service, but this action failed with the following error:
An instance of the service is already running."I am also getting a ton of Spooler errors I assume due to the service stopping and the drive being unavailable. When Virtual Disk Service is running everything is fine. It's definitely what's causing this problem but I don't know what is triggering it to die.
-
Who would have guessed, Backup Exec causing a problem
-
@scottalanmiller said:
Who would have guessed, Backup Exec causing a problem
I'm not so sure it is now. I turned off the backup server entirely and still ran into the Virtual Disk Service Crashing
-
@wirestyle22 said:
@scottalanmiller said:
Who would have guessed, Backup Exec causing a problem
I'm not so sure it is now. I turned off the backup server entirely and still ran into the Virtual Disk Service Crashing
Is that crashing in the hypervisor? or inside the VM?
-
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
Who would have guessed, Backup Exec causing a problem
I'm not so sure it is now. I turned off the backup server entirely and still ran into the Virtual Disk Service Crashing
Is that crashing in the hypervisor? or inside the VM?
It's not even in a VM it's a standalone server. Both the file server and the backup server.
-
@wirestyle22 said:
It's not even in a VM it's a standalone server. Both the file server and the backup server.
That would be the first problem
-
@scottalanmiller said:
@wirestyle22 said:
It's not even in a VM it's a standalone server. Both the file server and the backup server.
That would be the first problem
One step at a time
-
Anything else weird about the box? No RAID, software RAID or something like that?
-
@scottalanmiller said:
Anything else weird about the box? No RAID, software RAID or something like that?
Agreed -
A one second google search makes me ask - do you have a bad drive? could you have a failing RAID card/storage controller?
-
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
-
Failing memory on the RAID card would be a key suspect too.
-
@scottalanmiller said:
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
Man, trouble shooting that has to be a huge pain!
-
@Dashrender said:
@scottalanmiller said:
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
Man, trouble shooting that has to be a huge pain!
Thankfully ECC memory tends to catch it. Have it happen without ECC memory and you are in deep doo doo. It can cause ANYTHING to happen. Random crashes and file corruption are most common, but the scary things are time leaps, miscalculations, and things like that.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
Man, trouble shooting that has to be a huge pain!
Thankfully ECC memory tends to catch it. Have it happen without ECC memory and you are in deep doo doo. It can cause ANYTHING to happen. Random crashes and file corruption are most common, but the scary things are time leaps, miscalculations, and things like that.
Is there a log when ECC does it's job?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
Man, trouble shooting that has to be a huge pain!
Thankfully ECC memory tends to catch it. Have it happen without ECC memory and you are in deep doo doo. It can cause ANYTHING to happen. Random crashes and file corruption are most common, but the scary things are time leaps, miscalculations, and things like that.
Is there a log when ECC does it's job?
Yes, in the ILO on a Proliant.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
And, one that SMBs never seem to see but I've seen a lot in the enterprise, is a failing memory chip can cause crazy stuff to happen.
Man, trouble shooting that has to be a huge pain!
Thankfully ECC memory tends to catch it. Have it happen without ECC memory and you are in deep doo doo. It can cause ANYTHING to happen. Random crashes and file corruption are most common, but the scary things are time leaps, miscalculations, and things like that.
Is there a log when ECC does it's job?
Yes, in the ILO on a Proliant.
That's very interesting as this is a ProLiant by chance. Good to know. I'm going to run a lot of tests tomorrow. It's a very odd issue. Too much to do and not enough time to do it
