"Automation server can't create objecttsc.js"

Topics: General
Nov 19, 2013 at 11:49 PM
Edited Nov 19, 2013 at 11:51 PM
I'm trying to deploy my solution to Azure using the brand spanking new TS 0.9.5 beta. (Thanks, guys!) However, I'm getting the following error message during the Kudu build process. Note that this only seems to happen on Azure, not during local builds, or even while running "deploy.cmd" locally:

Building TypeScript: Payboard.Site.js (using ..\typescript\tsc.exe)
Building TypeScript: Payboard Widget (using ..\typescript\tsc.exe)
Building TypeScript: App\Payboard.App.js (using ..\typescript\tsc.exe)
tsc.js(59664, 13) JavaScript runtime error : Automation server can't create objecttsc.js(59664, 13) JavaScript runtime error : Automation server can't create objecttsc.js(59664, 13) JavaScript runtime error: Automation server can't create object

Because I couldn't figure out any other way to do it (open to suggestions!), I've included the TypeScript tsc.exe (and supporting files, such as lib.d.ts, tsc.js, and tschost.dll) within my source code, so that I could call it from my "tsbuild.cmd" and have some reasonable guarantees that it was going to be there on the Azure build server and was going to be the right version. So my "tsbuild.cmd" looks like so:

set tsc=..\typescript\tsc.exe
echo Building TypeScript: Payboard.Site.js (using %tsc%)
%tsc% --sourcemap --out Scripts\Payboard\Payboard.Site.js @tsbuild_Site.txt echo Building TypeScript: Payboard Widget (using %tsc%)
%tsc% --sourcemap --out Widget\v1.0\Payboard.js @tsbuild_Widget_v10.txt echo Building TypeScript: App\Payboard.App.js (using %tsc%)
%tsc% --sourcemap --out App\Payboard.App.js @tsbuild_App.txt Any troubleshooting suggestions?
Nov 19, 2013 at 11:59 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Nov 19, 2013 at 11:59 PM
Thanks for the report - copying over to work item so we can investigate.
Nov 20, 2013 at 12:03 AM
One possibility - perhaps a strong possibility - is that the tschost.dll is (now?) an automation server, and hence needs to be registered, not just present. If that's the cause of this, that kinda breaks my scenario, as I (quite properly) don't have permissions to register an automation server on my Azure build server.

So maybe this is another way to phrase my question: What's the best way to run TS builds during a deploy to Azure via kudu?