After I capture MS Project or Visio 2010, and I follow the changes on the Office 2010 the rebuild bacth file finds white space on certain lines in the txt files.
Even if I don't follow the KB on Office 2010 and do a regular build with no changes, I still get the white spaces. Any fix?
Open a command prompt at the root of your project.
Run build.bat
One of the first things that happens in the build process is the import of the virtual registry. Depending on the speed of your system you may or may not see the white space errors listed right off the bat. Hit CTRL+C and kill the build as soon as the registry import is finished. Scroll up and the error codes will tell you the line number(s) containing white spaces.
In Notepad you can go to a line number in the appropriate virtual registry text file by clicking Edit -> Go To. Input the line number from the error in the command prompt window. Remove white space from the end of that line.
I usually see these white spaces at the end of ProxyStubCLSID type of entries. There's usually three lines that have this issue, and they are usually within twenty rows of each other.
Thanks Toby, I will try it out and let you know I find. I read in the community that a few people are running into this but where not posting the fix. Even if I do a native build, it gives whitespaces. Researching the cause of this now.
I'm not sure if the cause is known. I see the white spaces in any ThinApp 4.7.x build of either Visio 2010 or Project 2010 (or both) regardless of capture machine OS and configuration.
Can someone post a screen shot of the symptoms/issue?
I assume this is what we are discussing (below link) but I want to be sure.
http://blogs.vmware.com/.a/6a00d8341c328153ef0133ef1f3bdd970b-pi
The white spaces I believe that are being discussed here are different. When first running build.bat on Visio 2010 you will see things mentioned during the virtual registry import, like: "White space at end of line 15281 in HKEY_LOCAL_MACINE..." Like I mentioned in my earlier reply, I always have three of these lines with Visio 2010, and they always involve ProxyStubCLSID entries. Maybe I can get a screenshot up on Tuesday.
Ok guys thanks I was able to remove the whitespaces with Notepad++.
Thanks for posting the pics! The weird thing is I'm not able to recreate this in my lab.
Can someone share their capture environment config?
Hello,
Windows XP SP3 (no patches)
.Net 3.5 in base with the .Net patches
Windows XP SP3 (fully patched)
.Net ALL
Bunch of other apps; adobe, MS Visual C++ 2008 Redstributable, View Client, VMware Tools, MSSE, Java 6 update 29, Checkpoint JUNK, 7-Zip
I see the same issue though I am not sure which Thinapp version this started in. As in the guzzom's screenshot every line where there is a white space is after a registry key ending in "ProxyStubClsid". There are 3 instances of this in my case. Removing the white space fixes the problem. I would guess that this happens when the capture folder is built.
