DDE Server Windows:orcascr9.exe: Application Error

I've looked at the queries on SO that pertain to similar errors - but haven't found anything so far, to help with this particular problem I am having with an orcascript which I am running under Powerbuilder9.0. The orca script connects to an SCC service provider, does a full target refresh, and then is supposed to build the exe. It never gets to the last step though.

The log is not very informative and simply says this at the point of failure: PBORCA_SccRefreshTarget. Full Rebuild Calling cm_rebuild_application(CM_REBUILD_FULL) While the script is at some way into this above step, it exits and throws up the DDE server error.

Can someone help me figure this one out? I just barely know the basics of PB, and the intent of this exercise is to convert an IDE-based build that I inherited, into an orcascript build so that i can run the build unmonitored.

Thanks in advance!

EDIT: I am now running Performance monitor per suggestion below, and here is what I see for the orcascr9.exe process at the point of failure.

Class:Filesystem

Operation: QueryAllInformationFile

Result:BUFFER OVERFLOW

Path:c:\.s\00019\MORENUM开发者_如何学GoBERSblah.pbl

So, I haven't heard a follow up of whether the build is successful in the IDE or not, so I'm going to make suggestions on the assumption that the IDE fails too.

There are a whole series of suggestions that I list at the Troubleshooting Guide on my site. In descending order of importance, the ones I'd particularly look at are:

• Optimize all your PBLs (yes, you'll have to do this one PBL at a time unless you've got a tool like PowerGen; then again if you've got PowerGen, I wouldn't recommend wasting time on ORCAScript)
• Full Build from within the IDE, making sure Informational messages are turned on (Options menu item from the Library Painter... it used to make sense, but not so much any more); try to address all issues reported
• Look for multiple versions of your PowerBuilder DLLs on your system
• Get rid of duplicate objects

If you're still having problems after these steps, there may be other ideas in the Troubleshooting Guide that may inspire some ideas, but I'd be running out of ideas based on the information available to date.

Good luck,

Terry.

You can try to determine the object the build is dying on. One approach is to take a look at the last-modified library. The object the build is dying on will have an older compile date than the build, as will any that the build hadn't gotten to. That may help you narrow things to a few likely suspects. Absent source control I'd suggest shuffling half the non-compiled objects at a time to a different pbl until the build fails on a different pbl. Then you start moving objects from the last batch the other way. You could copy the pbls and experiment with a regular non-scc build in orcascript but that's a lot of extra work and if the non-scc build works, you'll have a larger mystery instead of a solution.