Book a Demo

Author Topic: Attempting to debug script: MS PDM creation failed  (Read 3766 times)

mmo

  • EA User
  • **
  • Posts: 85
  • Karma: +0/-0
    • View Profile
Attempting to debug script: MS PDM creation failed
« on: July 20, 2014, 06:45:44 pm »
I was trying to debug a script that doesn't behave as expected, but when click the Debug - button all I get is:

----------------------------
[68746974]      Stack recording threshold set to 3 frames
[68747038]      Default Directory is C:\Users\moserm\Desktop
[68747038]      Agent dll found: C:\Program Files (x86)\Sparx Systems\EA\VEA\SSScriptAgent.DLL
[68747038]      Default Directory is C:\Users\moserm\Desktop
[68747039]      Agent: Started
[68747118]      Microsoft Process Debug Manager creation Failed: 0x80040154
[68747118]      This is included as part of various Microsoft products.
[68747118]      Download the Microsoft Script Debugger to install it.
[68747119]      Failed to initialize VBScript engine
----------------------------

What is going wrong here?

This is using EA 10 (Corp. Edition) on Windows 7 Enterprise.

M.
 :-/

Tehila1

  • EA User
  • **
  • Posts: 256
  • Karma: +0/-0
    • View Profile
Re: Attempting to debug script: MS PDM creation fa
« Reply #1 on: July 20, 2014, 07:08:27 pm »
As far as I understand you would like to debug a simple script.
  
Try this sample , it was taken from this form, tested and works fine to me:  
  
The selected package name should be displayed in a message box
Code: [Select]
sub main
      FuncName()
end sub
Function FuncName()
      ' Repository object was set before invoking the script!
      ' Get the currently selected element in the tree to work on
      dim thePackage
      set thePackage = Repository.GetTreeSelectedPackage()
      
      if not thePackage is nothing then
      MsgBox(thePackage.Name)
            FuncName= thePackage.Name
            
      end if
End Function
main

mmo

  • EA User
  • **
  • Posts: 85
  • Karma: +0/-0
    • View Profile
Re: Attempting to debug script: MS PDM creation fa
« Reply #2 on: July 20, 2014, 08:13:23 pm »
Hi Tehila,
thanks for responding!

Sorry, the point was not, to obtain some output (I know how to do that and - in fact - I got my script working in the meantime using misc. debugging output statements - see my other thread).

The point was, that the real debug-functionality (you know, supporting single-stepping, inspecting variables, etc.) that is supposed to work for EA scripts, obviously does not, because some library or whatever seems missing. That would, however, be handy when debugging more complex scripts.

Regards and thanks,
M.