WAB blocking processes and not starting

[RichardHughes]

I've installed the latest version of WAB onto windows 7 and have node version 4.2.2LTS installed on the system.  I am able to run MongoDB, grunt, and dojo build all on Node without issues.  When I install WAB it initially boots up quickly.  Eventually when I startup the server.js file either using command line or with the startup.bat, the WAB startup seems to block all processes on my pc and the browser freezes.  The NT Kernal is getting jammed.  The program does not load.  When I close the Command Prompt and kill the WAB server, the pc immediately jumps back into action.

Has anyone else experienced this behavior with node.js or the WAB?  Is this an issue with running on Windows?

[RebeccaStrauch__GISP]

Richard, just FYI, when I open WAB the second time it is fast with the load, but I do not have many apps built yet.  Edit: but it does need to load any/all custom widgets first.

can you try making a current version of FireFox the default temporarily to see if you have the same sluggish start up?

[RichardHughes]

I set Firefox as the default browser and my log file is below.  The loading page loads for WAB but each javascript file is taking several seconds to load.  It would take minutes for all of them to load.

[2015-11-11 08:59:37.461] [INFO] repo - Read repository items: C:\CODE\arcgis-web-appbuilder-1.2\client\stemapp\widgets

[2015-11-11 08:59:38.833] [INFO] repo - Read repository items: C:\CODE\arcgis-web-appbuilder-1.2\client\stemapp\themes

[2015-11-11 09:00:03.382] [INFO] server - No portal URL is set, redirect /webappbuilder to /webappbuilder?action=setportalurl

[2015-11-11 09:00:33.346] [INFO] server - Set isXT = true;

[RobertScheitlin__GISP]

Richard,

   Based on your log you have a couple of custom widgets in your widget folder. Try try removing all custom widgets and try again with a 100% vanilla WAB install. Once you get your portal url set and WAB running then you can add custom widgets.

[AhjungKim4]

I had the same issue; none of the WAB 1.x versions would open internet browser, and it also slowed down all other processes.  I fixed the issue by adding the node.js file shipped with the WAB as allowed program through Windows Firewall.

• Windows Firewall
• Allow a program through Windows Firewall
• Allow another program
• Browse to your extracted WAB folder > server > node_for your system.js.