Guest file indexing

[snowmizer]

I have guest file indexing enabled on my Veeam jobs so that people can use the 1-click restore from the enterprise manager. All jobs are working fine with the exception of one. I have a job that has 4 servers and 3 of the 4 servers index fine. The 4th fails with the message:

Failed to index guest file system
Error: Cannot read data from volume
Win32 Error: : The handle is invalid
Code: 6

I have asked support about this but have been told that this is a Windows message so they couldn't give me any help. Has anyone else seen this error or can you at least point me in a direction on what Veeam is doing so I can try to figure this out?

Thanks.

[Gostev]

Did you run error checking on that disk from within guest?

[johan.wauters]

I have the same problem.

--> Did checkdisk on all disks
--> reinstalled VMware latest client
--> delete veeam backup job and created a new one
--> reboot VM machine + run all MS updates
--> 12 other VM machines are OK

Please some advice THX ! ! !

[pama]

The same for me!

OS: Windows 2003 standard, 32 bit

Upgrade from Veeam 5 to Veeam 6, never had this error when backupping with Veeam 5.
TY

Andrea

[theovds]

Same problem here. VM is a Windows 2003 terminal-server.

[Gostev]

Everyone, there is absolutely no point of posting "same problem" in this topic. This does not add any value to the discussion whatsoever. As with any technical issue, you should instead open a support case and let our technical staff investigate this for you with the full log files.

Also, please always be including you support case IDs when posting about any technical issues, otherwise this thread will be removed as per forum rules. This is needed so that we are able to lookup the resolution when future readers ask.

Thank you for understanding.

[snowmizer]

I did open a ticket on this issue (as well as another issue). The ticket #is 5159196. The response I got from support on this issue was that the tech support person wasn't sure about the indexing error because it was a Windows error. Not much help.

As far as the suggestions that were posted here. I had already re-created the job in version 6 and still get this error. I haven't run check disk or re-installed the tools. Now that you mention the tools install I know that when this server got moved the tools were out of date when we moved this server from VMWare 3.5 to vSphere 4.1. It looks like this server has been updated since then as the tools are showing "OK" and the hardware version is now 7. I'm wondering if this will be resolved if we uninstall the tools then re-install them this weekend when the next round of MS updates are applied.

Thanks for the suggestion.

[Gostev]

No, judging on the error, updating VMware Tools will not help. It looks like there is something in the actual file system causing this. Thanks for the support case number, I now have something to chase our support with.

[snowmizer]

Thanks. I would appreciate any help I can get with this message. I uploaded all of the relevant logs for this job last week.

[ec-inflxx]

Same issue. Worked fine with v5, but after upgrade to v6 only two of my 30+ VMs started getting this indexing warning.

Opened a case ID#5159253. Tech wanted me to look through the Windows Event logs but I didn't find anything. He was going to escalate the case.

[snowmizer]

I got a reply from tech support late yesterday. It appears they are aware that there are other people with this issue and they are trying to track down the cause. If I find anything out I will post here.

Thanks everyone.

[Gostev]

The pilot version hotfix was already available yesterday. Be sure to be checking the sticky topic on the known issues occasionally

[snowmizer]

If we have a support ticket open will we receive notification when the hotfix is available?

[Gostev]

Sure thing. Support folks are measured on the number of resolved cases anyway

[crawc]

Same issue. Worked fine with v5, but after upgrade to v6 I get the index issue. Windows 2003 Server, IIS converted from a physical machine.
I will watch this for hotfix.

[kstyrvoll]

Did the hotfix fix the issue? After I upgraded from v5 to 6 one of my guests started to report this error.

[Vitaliy S.]

Kristian, have you had a chance to open a support ticket on your issue?

[kstyrvoll]

I have not open any support case yet. Just wanted to check if people in this forum had solved their problem. I will collect logs and open a case.

[Gostev]

Yes, Patch 2 does resolve this issue.

[Franklin]

Where to get this patch?
I opened a support case wich isn't necessary if i could download this patch somewhere.

Ticket number: 5166331

[foggy]

Currently the patch is available through technical support only. Thanks.

[George]

Hi Guys,

Was wondering if there were any update on this?

Is there a hot-fix i can download somewhere or anything along those lines?

Thanks

[Vitaliy S.]

You can get it through our technical support. Thanks!

[homerjnick]

Has the hotfix been released?

I am getting this error on my jobs...

[foggy]

See the topmost sticky topic on this forum.

[homerjnick]

The hotfix was supplied to me and works, thanks.

[biker]

I had the same problem after the upgrade to veeam 6.
I've just installed the hotfix, i hope that i'll never see this warning again.