I just installed the latest version of SDT.
I am receiving a series of errors when accessing the tool.
An open operation on table 'MBS_AutoSetup_Cache' failed because the path does not exsist.
not sure what path or where it is located.
Thanks
*This post is locked for comments
This issue is resolved in the Build 16 hotfix
blogs.msdn.com/.../support-debugging-tool-build-16-hotfix-released.aspx
Hi everyone
I have fixed the issue with the period (.) in the filenames. I was not able to test it with a domain name, but it works now when a directory has a period in it when it would fail previously.
If you would like to test this hotfix, please email me at David dot Musgrave at Microsoft dot com.
Thanks
David
Hi Jennifer
The ctree caching tables in the Debugger folder underneath the share location's folder are new to build 16. These give significant performance improvement when reading data as reading the ctree cache files is much faster than reading and interpreting the XML setup file.
When saving changes, they are written to both the ctree caching tables and to the XML setup file.
It seems that the Dexterity filehandler for ctree tables does not like the periods in the machine name. This is a Dexterity issue and not a bug with SDT code. I will probably add a check into the SDT code to avoid the issue.
David
I also had this same problem. I was upgrading to build 16 from a previous version and had the debug path setup with the previous build with periods in the path name. I got those errors about path not existing and changed the path to use the servername instead. It is now working. So, it seems something got changed with build 16 that it now doesn't like having periods in the debug path name.
I was able to get it to work by using servername instead of DNS gpreports.si.us.lan
seems to be issue with periods in path name.
Thanks for the help
Thanks again
I will look at the code and see if the issue with the periods is something I can fix or whether it is a limitation of Dexterity.
The Debugger_<User>_<Company>.log files are created as the SDT logs various activities. It does depend on what you have the SDT doing.
Open the files and have a look.
You can always delete them.
David
Bingo, that was it; thank you. The only time I can see that being an issue is when using GP on a computer that is not a member of the domain. For us that won't be an issue, but that may be an issue for other users. May I suggest that as a bug/feature request for the next version?
On another note, I noticed that I'm getting a bunch of "debbuger_user_company.log" files in the shared SDT location. Will those stop now that I've fixed the error above?
Can you access the machine without the domain name? wondering if the periods are causing the problem?
David
I am able to create a file within the debugger folder with no issues.
MBS_Debug_Path=\\ralph.sscorp.com\intyshare\SDT_Settings\
That is the path to the SDT settings. I did delete the debugger folder in the above path to see if the SDT would re-create it, and it did, but the errors continued.
#1
André Arnaud de Cal...
292,865
Super User 2025 Season 1
#2
Martin Dráb
231,723
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
