Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9539

Quality Center Plugin Error: runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection'

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • qc-plugin
    • None
    • Windows Vista Enterprise SP2 x64
      Mozilla Firefox 4.0 & Internet Explorer 8
      Jenkins ver. 1.409
      qc plugin 1.0 (script runTestSet.vbs used is version fixed in issue #9267)

      ERROR trying to create the object TDApiOle80.TDConnection in Class QCTestRunner.

      Sub Class_Initialize
      errors = 0
      Set tdConnection = CreateObject("TDApiOle80.TDConnection")
      timestamp = CStr(Now)
      End Sub

      Error message reported is next:

      [TRUNK] $ cscript /nologo xxx\runTestSet.vbs http://xxx/qcbin pablo.garcia_hp.com ******** xxx xxx "xxx" Test1 qcreport-Test1-7.xml
      xxx\runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection'

      Cant create TDConnection Object

          [JENKINS-9539] Quality Center Plugin Error: runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection'

          Pablo García added a comment -

          Thanks to you.
          Perfect, i can test your patch under my environment.
          But i'm trying to prove the current version in a x86 SO with the same version tools to be sure that it's is the cause.

          Regards.

          Pablo García added a comment - Thanks to you. Perfect, i can test your patch under my environment. But i'm trying to prove the current version in a x86 SO with the same version tools to be sure that it's is the cause. Regards.

          David del Rio added a comment -

          Not sure if you guys have already fixed this--but I have a fix which is working for me. I'm successfully running on a 64-bit OS. I'm unfamiliar with the process, so please contact me if you haven't already addressed the issue.

          David del Rio added a comment - Not sure if you guys have already fixed this--but I have a fix which is working for me. I'm successfully running on a 64-bit OS. I'm unfamiliar with the process, so please contact me if you haven't already addressed the issue.

          Ever Tang added a comment -

          Romain,I'm trying to get the plugin work on Windows64,and i am having similar problem. How do I change the path to cscript.exe, if that was the problem cause?

          Ever Tang added a comment - Romain,I'm trying to get the plugin work on Windows64,and i am having similar problem. How do I change the path to cscript.exe, if that was the problem cause?

          Romain Seguy added a comment -

          OK, let me code the fix based on the link Pablo provided. I've asked David to provide his fix but I've had no answer

          Romain Seguy added a comment - OK, let me code the fix based on the link Pablo provided. I've asked David to provide his fix but I've had no answer

          Anthony Carr added a comment -

          Could someone tell me if a fix/workaround is available for this issue?

          Anthony Carr added a comment - Could someone tell me if a fix/workaround is available for this issue?

          Michael Jones added a comment -

          I'm still having the issus Can you please share what u did to resolve problem? Thanks!

          Michael Jones added a comment - I'm still having the issus Can you please share what u did to resolve problem? Thanks!

          Mark Brown added a comment -

          Was there ever a solution to this issue? I am trying to set this up now on a new project and I keep getting this error. I am not sure how to point it to use the x86 version of vb from within Jenkins. Is there a class or script i need to modify to make this work?

          Mark Brown added a comment - Was there ever a solution to this issue? I am trying to set this up now on a new project and I keep getting this error. I am not sure how to point it to use the x86 version of vb from within Jenkins. Is there a class or script i need to modify to make this work?

          Sachin Chitre added a comment -

          This remains an issue even with Jenkins 1.519.
          The QC plugin is practially useless if this issue is not resolved.Seems this one is around since more than two years.
          Seems like a quick fix to run the 32-bit cscript or wscript command from within the Jenkins plugin code on detecting a 64-bit platform.
          Can someone mercy upon us!
          Thanks in advance

          Sachin Chitre added a comment - This remains an issue even with Jenkins 1.519. The QC plugin is practially useless if this issue is not resolved.Seems this one is around since more than two years. Seems like a quick fix to run the 32-bit cscript or wscript command from within the Jenkins plugin code on detecting a 64-bit platform. Can someone mercy upon us! Thanks in advance

          Benjamin Mahr added a comment - - edited

          Have the same problem with calling vb-script (seems to be a principal problem, not directly related to qc-plugin) on Jenkins 2.116, Windows 10 Pro 64bit running as service on admin account with full rights. I think its also related to this 32/64bit issue, but now workaround was helping me till now.

          Microsoft VBScript runtime error: ActiveX component can't create object: 'Excel.Application'

          See attached files.

          We really looking foward to a fix because we try to automate our translation while producing our nightly build.

           

          Benjamin Mahr added a comment - - edited Have the same problem with calling vb-script (seems to be a principal problem, not directly related to qc-plugin) on Jenkins 2.116, Windows 10 Pro 64bit running as service on admin account with full rights. I think its also related to this 32/64bit issue, but now workaround was helping me till now. Microsoft VBScript runtime error: ActiveX component can't create object: 'Excel.Application' See attached files. We really looking foward to a fix because we try to automate our translation while producing our nightly build.  

          Benjamin Mahr added a comment -

          Additionaly it seems the workaround by calling a 32bit cscript directly is not working. I attached a fixed example batch file.

          Benjamin Mahr added a comment - Additionaly it seems the workaround by calling a 32bit cscript directly is not working. I attached a fixed example batch file.

            danielpetisme Daniel Petisme
            pgarcia Pablo García
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: