View Single Post
  #1  
Old 04-09-2008, 01:11 PM
Adarnvoid Adarnvoid is online now
Registered User
 
Join Date: 04-09-2008
Location: Canada
Posts: 3
Split from thread http://www.kinook.com/Forum/showthre...?threadid=3440

I appear to be experiencing a similar problem. However, my problem appeared after I changed PCs. Both my old and new computers were running Win XP SP2, and I had very similar array of software on both machines. The only significant difference (and this may be a red herring) is that the new machine is a dual core. Here are some details about how this problem presents in my case...

• Appears in both VBP 6.4 and 6.7
• There are ~20 developers at my site building the same steps on a regular basis (none have experienced this problem). The other developers are:
o using both VBP 6.4 and 6.7
o using Win XP, Vista, maybe some Win 2000 left
o some are using dual core machines some are not
• Using the VBP GUI I'm building a subset of steps (~150 steps out of a total of ~2300)
• The steps being build are all VS6 and VS.NET
o Don’t think I have seen a freeze on a VS.NET (but represent < 5% of steps)
• Typically it will freeze on 4 – 8 of the ~130 steps being build
• When a freeze occurs:
o It happens after project is compiled and linked (95% are .DLLs or .ENUs) the “Performing registration” step appears in the Output window in VBP.
o There is no significant VBP, compiler, or linker activity (in the CPU cycles)
o I have to stop the build (it takes maybe 5-7 seconds typically) then I get the following message in the Output window:
 Error firing vbld_StepDone event: Error in System (VBScript) script code at Line 383, Column 1 (timeout)
o I then restart the build and the step will complete without issue (although typically freeze on some later step in the build).

I have attached an excerpt from the Output window (see attached OutputWindow.rtf). I can also attach the .bld file but I want to make sure that will be private first (this is my first post to this forum so I’m still learning). Providing the source being compiled will be a little bit more complicated, because there are issues of propriety and licensing for required third party libraries; but if it becomes necessary for your (Kinook) to build this in order to diagnose the issue we can probably arrange that.

Please let me know if you require any further information.

-Thanks
Attached Files
File Type: zip outputwindow.zip (8.1 KB, 956 views)
Reply With Quote