Hello, I've just installed Starteam 2006 cross platform client and our finalbuilder project (5.5.0.244) does not work anymore. To isolate the problem, i created a single "Run Script" action like : Dim lSTFinder, lSTView Set lStFinder = CreateObject("StarTeam.StStarTeamFinderStatics") Set lStView = lStFinder.openView("user:pwd@server:49201/...") <- Error here set lStView = nothing Set lStFinder = nothing
Running the action raise the error: VBScript error line 3 : Automation is not managed by this class (my english translation)
- If i try to instanciate old SDK class (StarTeam.StStarTeamFinderStatics.11) it works for this method, but it failed later with the same msg, when using lStView, - Running the script in a vbs, outside FinalBuilder, is OK,
- i did not found anything about this bug in google, - Our FB project running on a server where ST client has not been upgraded is still working, even if it is connecting to the Starteam 2006 Server, - We have the same issue on another client laptop where ST client have been upgraded,
This issue is really blocking for us, since i do not see any workaround.
it would be helpful if we can know if someone can reproduce the problem or if someone managed to use successfully ST2006 SDK from FB scripts.
The script you gave is working for me here. The error appears to indicate that (possibly) a COM object was not registered properly. Have you tried installing on a machine which does not have an older version of the ST client and SDK already installed, or uninstalling and then reinstalling all StarTeam programs and the SDK?
I can't explain why the code works properly from the .VBS file but not from FinalBuilder, in theory both of them should be using the exact same methods to execute the lines of script and to instantiate the object.
A workaround may be to call the .VBS file from FinalBuilder, using the Execute Program and cscript.exe, or to make a .NET custom action package which utilises the .NET API.
hello, Thanks for testing. Indeed, uninstalling SDK 6.0 correct the problem that i described first. In fact, the error occurs as soon as there are 2 SDK installed on the client, i saw the issue with : - SDK 6.0 and SDK 9.3 - SDK 9.1 and SDK 9.3
This is quite strange because everything seems ok outside FB. Nevertheless, uninstalling an old SDK raised another issue about SCC provider, but it does not concern this forum :).