topic Re: Web AppBuilder Install Nightmare in ArcGIS Web AppBuilder Questions

Web AppBuilder Install Nightmare

AndrewMilanes — Mon, 22 Dec 2014 23:29:08 GMT

I can't seem to get the released version of Web AppBuilder installed as a service. I had to change to port 3347, since the beta version ran on 3344. Don't know how to release that port. I can get the new version running from the startup.bat file after changing the port. I can also get the service installed, but it won't start. Is it because it's trying to use port 3344? Where can you change the port when you install as a service?

This install is a major pain in the rear.

Re: Web AppBuilder Install Nightmare

RobertScheitlin__GISP — Tue, 23 Dec 2014 02:13:08 GMT

Andrew,

Are you needing to run both the Beta 3 and the Version 1.1 at the same time (meaning having both WABs running simultaneously)? If not then you do not need to change the ports at all. I can run Beta 3 one time and then close it and run 1.1 the next and not worry about changing anything.

Re: Web AppBuilder Install Nightmare

AndrewMilanes — Tue, 23 Dec 2014 13:31:46 GMT

Thanks for your help Robert. No I do not want to run the beta as well. But for some reason when I try to run the release version it says port 3344 is in use. I ran a port scan and can't find anything using it, so I attributed it to the beta1 somehow holding onto ports 3344-3346.

Re: Web AppBuilder Install Nightmare

RebeccaStrauch__GISP — Tue, 23 Dec 2014 16:25:35 GMT

For what it's worth Andrew, mine shows the same ports 3344-3346.

I know for me (and this happened in beta too) sometimes when I start WAB, it opens the WAB command window but doesn't start up the app in the browser (I'm using Firefox), if I close the WAB/nodejs command window, and then just restart WAB, it will fire up in the browser. I sometimes also make sure that FireFox has the focus, but I don't know that it makes a difference.

Also, as Robert Scheitlin and others have pointed out in other threads, if you use Brackets, you may want to make sure that is closed (that was for beta....not sure if it still applies).

Re: Web AppBuilder Install Nightmare

RobWaller — Tue, 23 Dec 2014 21:33:03 GMT

Not sure if related, but had similar issue in Beta 2. Turned out the startup.bat wasn't checking for '3344' string for exact match, but any part that matched. I had a Server SOC process that was running on 63344, and that kept the startup.bat from passing the port test and kept getting that message. If examine startup.bat can see that that message comes from failing the port test.

In that version I edited the startup.bat to make sure was looking for exact match, do you have other processes running on port that contains '3344' somewhere.

Edit: To test this use the netstat command, this is what the startup.bat does:

netstat -aon | findstr "3344"

Re: Web AppBuilder Install Nightmare

AndrewMilanes — Tue, 23 Dec 2014 22:01:11 GMT

That's a good point Rob. I'll have to check.

Re: Web AppBuilder Install Nightmare

MohammedKabeer — Mon, 29 Dec 2014 06:52:25 GMT

Dear Sir,

i am facing same problem when i run netstat -aon | findstr "3344"

here is the result. how can i change the ports

i can run webappbuilder from portal but not from my local machine

Thanks

Kabeer

Re: Web AppBuilder Install Nightmare

AndrewMilanes — Tue, 06 Jan 2015 19:59:28 GMT

Still can't get the service to start. "Windows could not start the ArcGISWebAppBuilder service on Local Computer"

Don't know what else to do.

Re: Web AppBuilder Install Nightmare

AndrewMilanes — Wed, 07 Jan 2015 14:15:55 GMT

Tried to install on a different server. Still unable to start the service.

Re: Web AppBuilder Install Nightmare

RobertScheitlin__GISP — Wed, 07 Jan 2015 14:35:40 GMT

Andrew,

When you say "Server" do you really mean that you are attempting to install WAB Dev edition on a Windows server? If so this is likely an issue as Windows server will have mush tighter security and port restrictions. A standard installation and workflow would be to install WAB Dev edition on a Workstation do all you configuration and or development and then download the finished app and take that zip files contents and move that to your production web server.

Re: Web AppBuilder Install Nightmare

AndrewMilanes — Wed, 07 Jan 2015 14:47:41 GMT

Yes, Windows Server 2008.

That explanation makes sense. We're not developers in the slightest, so this workflow would be new to us. We'll give that a shot. Thanks!

Re: Web AppBuilder Install Nightmare

JoshWhite — Thu, 02 Jul 2015 21:52:10 GMT

I have to agree with Andrew. I installed the WAB on my GIS Server thinking it had to be there to run the webmap (wrong because it actually runs through AGOL) but anyways now I always get the message that essentially says I cannot establish a connection on port 3344 even though it worked previously.

Re: Web AppBuilder Install Nightmare

RebeccaStrauch__GISP — Thu, 02 Jul 2015 22:50:09 GMT

If you haven't already, check out my blogs

Tips and Observations for getting Web AppBuilder - Developer Edition Installed

and once you start working with it. Web AppBuilder Developer Edition &#8211; Customization Resource List

these might help. the resource list has many links to custom widgets, etc.

Re: Web AppBuilder Install Nightmare

JoshWhite — Mon, 06 Jul 2015 13:14:47 GMT

Lots of good info, the instructions aren't very clear (on the site, not the blog), does this have to be on a machine that runs Windows Server or can everything be done from a workstation? I'm wondering about the second part of the below quoted post from Robert:

A standard installation and workflow would be to install WAB Dev edition on a Workstation do all you configuration and or development and then download the finished app and take that zip files contents and move that to your production web server.

Re: Web AppBuilder Install Nightmare

RobertScheitlin__GISP — Mon, 06 Jul 2015 13:23:06 GMT

Josh,

You can download and deploy your app on a standard Windows machine (non-server, assuming it has IIS). My comment was based on a normal production server environment.

Re: Web AppBuilder Install Nightmare

JoshWhite — Mon, 06 Jul 2015 14:58:16 GMT

Ok, that's what I needed to know, if IIS is required, I would need to figure out my security issue on the ports on my Windows Server machine. I put in an email to IT to see if they can assist me.

Re: Web AppBuilder Install Nightmare

RaymondGoins — Fri, 14 Aug 2015 12:52:12 GMT

I know this question is marked as answered but I found that the script is looking for the port as a LIKE instead of looking for the exact port as Rob pointed out. So port 13344 was open on my box and the script would fail.

To fix problem Edit the startup.bat file and change this line:

CALL :IsPortTaken %port%

(which is line 23)

to this

CALL :IsPortTaken port%

This will look for ports that start with 3344 but may still fail if you have port 3344x open

this would be best

CALL :IsPortTaken port

Since open ports are exact this would be the best option

Hope this helps

Ray

Re: Web AppBuilder Install Nightmare

JaclynMeade1 — Sun, 16 Aug 2015 19:43:50 GMT

I keep getting this error when trying to install. Any ideas?

Re: Web AppBuilder Install Nightmare

RobertScheitlin__GISP — Sun, 16 Aug 2015 21:20:08 GMT

Jaclyn,

Did you install NodeJS? Here is step 2 from the getting started guide: Get started—Web AppBuilder for ArcGIS (Developer Edition) | ArcGIS for Developers

Because Web AppBuilder runs on top of Node.js, you must have Node.js installed on your computer. The download package contains the Windows version of node.js.
If you are on a Windows platform, you can follow the steps in the next section to start Web AppBuilder.
If you are on a platform other than Windows, such as Mac or Linux, you need to install Node.js specifically on your platform first. In case you already have Node.js installed, make sure its version is 0.10.0 and later.

Re: Web AppBuilder Install Nightmare

ColeAndrews — Wed, 16 Sep 2015 16:20:37 GMT

Anyone have a suggestion when the startup.bat file runs and opens the browser to "Page cannot be displayed"? This is before it properly loads Web Appbuilder Dev and prompts for Portal URL.