Unsolved
This post is more than 5 years old
2 Posts
0
951
DiskXtender for Windows 6.1 fails on startup
For almost as long as we have been running DiskXtender we have had an error message regarding a file path being too long for one of our wonderful users. Overall this seems to have had no effect on the functionality of DiskXtender and has not had an effect on DiskXtender starting.
DiskXtender as of today seems to be the source of lockups on our clients while browsing the server. If we stop and start the DiskXtender service the clients spring back into life.
So looking for a solution we discover there is yet another patch for this product so the patch is installed and rebooted the server.
We now get an error message popping up on the server:
Microsoft Visual C++ Runtime Library
Program: ...gram Files\EMC\DiskXtender\bin\DxDmService.exe
A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated.
This is not good and will pop up every time we restart the DiskXtender Service. As soon as the error is acknowledged (clicked on OK) the service stops. If you ignore the error message the service continues to run.
There is nothing in the logs or windows event logs. Any advice or assistance would be gratefully recieved.
Message was edited by:
OoKiE
DiskXtender as of today seems to be the source of lockups on our clients while browsing the server. If we stop and start the DiskXtender service the clients spring back into life.
So looking for a solution we discover there is yet another patch for this product so the patch is installed and rebooted the server.
We now get an error message popping up on the server:
Microsoft Visual C++ Runtime Library
Program: ...gram Files\EMC\DiskXtender\bin\DxDmService.exe
A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated.
This is not good and will pop up every time we restart the DiskXtender Service. As soon as the error is acknowledged (clicked on OK) the service stops. If you ignore the error message the service continues to run.
There is nothing in the logs or windows event logs. Any advice or assistance would be gratefully recieved.
Message was edited by:
OoKiE
OoKiE1
2 Posts
0
November 12th, 2007 13:00
Another typo fixed by:
OoKiE
bmeltzer
26 Posts
0
November 28th, 2007 08:00
Your users browse the DX server via Windows explorer as well, right?
Patch 8 for 6.10 addresses this issue and should be available via Powerlink.
I would also suggest that you get to a point where you eliminate file names and file paths greater then 256 characters
You should be able to find Microsoft articles on the consequences of MAX_PATH file names
Adam Hutcher
3 Posts
0
March 13th, 2023 03:00
Long Path Tool can help you to handle long path files: www.LongPathTool.com