Web AppBuilder

32888
62
07-03-2014 10:18 AM
PaigeSpee
Esri Contributor

Web AppBuilder is a configurable HTML5/JavaScript-based application that will be a new feature of ArcGIS Online and Portal for ArcGIS. It will help you create web apps without having to write any code.  Watch a demo of Web AppBuilder for ArcGIS | Esri Video presented by Esri Product Manager  Julie Powell at this year's DevSummit.

62 Replies
TarigAhmed1
Deactivated User

Hi Zhifang,

I did exactly what you said and I got the same error (see below):

C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\server>taskkill /F /PID 8080

ERROR: The process "8080" not found.

C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\server>taskkill /F /PID 8080

ERROR: The process "8080" not found.

C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\server>tasklist /FI "PID eq 80"

INFO: No tasks are running which match the specified criteria.

C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\server>tasklist /FI "PID eq 8080"

INFO: No tasks are running which match the specified criteria.

C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\server>node.exe server.js -port 80

[2014-07-30 09:07:41.710] [INFO] repo - watch repository change:  C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\client\stemapp\themes\

[2014-07-30 09:07:41.713] [DEBUG] repo - watch dir:  C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\client\stemapp\themes\

[2014-07-30 09:07:41.714] [INFO] repo - watch repository change:  C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\client\stemapp\widgets\

[2014-07-30 09:07:41.714] [DEBUG] repo - watch dir:  C:\inetpub\wwwroot\WebAppBuilder\Beta2\arcgis-web-appbuilder-1.0beta2\client\stemapp\widgets\

Server listening tcp connection on port 3344 in development mode

Server listening http connection on port 3345 in development mode

Server listening https connection on port 3346 in development mode

stream.js:94

      throw er; // Unhandled stream error in pipe.

            ^

Error: connect ECONNREFUSED

    at errnoException (net.js:904:11)

    at Object.afterConnect [as oncomplete] (net.js:895:19)

Thanks,

Tarig

0 Kudos
ZhifangWang
Esri Regular Contributor

Hi Tarig,

From your output above, it seems that you still run nodejs on port 3344/3345/3346,

1.jpg

It's my mistake that show you the wrong command to start nodejs on port 80, I've corrected the command in my original comment, the correct one should be:

"node_x86.exe server.js -port=80" or "node_x64.exe server.js -port=80"

If you run nodejs on 80, you should see output as below:

2.jpg

If you successfully start nodejs on port 80, please enter "http://yourmachinename/webappbuilder" in your browser and try to see if you could log into Portal.

Thanks!

0 Kudos
TarigAhmed1
Deactivated User

Hi Zhifang,

I followed your instructions above, but the nodjs on port 80 didn't start (see attached screen shot). no idea what that means.

Thanks

TarigimageFile.png

0 Kudos
ZhifangWang
Esri Regular Contributor

Hi Tarig,

The error message

"

[2014-08-01 13:42:58.191] [DEBUG] repo - watch dir:  D:\git projects\arcgis-weba

ppbuilder\client\stemapp\widgets\

register /dojo -> D:\git projects\arcgis-webappbuilder\client\libs\dojo

events.js:72

        throw er; // Unhandled 'error' event

              ^

Error: listen EACCES

    at errnoException (net.js:904:11)

    at Server._listen2 (net.js:1023:19)

    at listen (net.js:1064:10)

    at Server.listen (net.js:1138:5)

    at Object.<anonymous> (D:\git projects\arcgis-webappbuilder\server\server.js

:139:24)

    at Module._compile (module.js:456:26)

    at Object.Module._extensions..js (module.js:474:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

    at Function.Module.runMain (module.js:497:10)

"

can occur when the port 80 is using by another process, such as IIS, please check your port 80 is available before you try "node_x86.exe server.js -port=80".

Thanks.

0 Kudos
TarigAhmed1
Deactivated User

Hi Zhifang,

Still the same error (see attached screenshot)

  1. I stopped the IIS and, that did free port 80
  2. ran:  node_x86.exe server.js -port=80
  3. went to http://localhost/webappbuilder
  4. Entered the   https://nttagis.maps.arcgis.com/home/ succesfully
  5. Still got the same error when I enter my user name / password.

node_x86.exe server.js 80 Portal login.png

Thank you,

Tarig

0 Kudos
AlexisRodriguez
Occasional Contributor

Hi Tarig,

As I commented in other post you have made, our team was experiencing exactly the same issue as you. Every screenshot you have posted gives same error messages than ours.

Yesterday we found out that the reason why we could not log in properly was the fact that we were working behind a corporative proxy. If you sniff all http requests while using app builder you'll see that portal url checking is made by the browser directly (browser knows we are behind a proxy) and that's why you've got a green check after validated. However, credential validations are made through a javascript class ("proxy.js") where the connection is lost, throw an error of access and shutdowns the nodejs server.

We tried same webapp in a machine outside the office and everything worked fine. We were able to log in properly and start using it!

We have already reported this bug to Esri Beta Community and I opened another discussion in GeoNet asking for solutions to configure WebAppBuilder so as to work behind a corporative http proxy.

Working with WebAppBuilder behind a corporative http proxy

Therefore, please, check if you are working in the same scenario than us.

Thanks,

Alexis

0 Kudos
TarigAhmed1
Deactivated User

Hi Alexis,

Thanks that was very helpful. I'm sure ESRI will come up with something, almost all organizations have some sort of a proxy setup these days.

I have also reported it to ESRI Beta Community.

Hope to hear back from ESRI soon.

Thanks

www.linkedin.com/in/tarigahmed/

0 Kudos
ZhifangWang
Esri Regular Contributor

Hi Tarig,

Your steps is very clear and is helpful for us to research the reason. As Alexis Rodriguez‌ said, are your network traffic all go through some sorts of proxy? If this is the case, please keep eyes on Working with WebAppBuilder behind a corporative http proxy‌ this thread, we are trying to find a solution to the proxy issue.

Thanks!

0 Kudos
AlexisRodriguez
Occasional Contributor

Hi Tarig, hi Zhifang,Workaround given in Working with WebAppBuilder behind a corporative http proxy‌ worked for us! So, Tarig, check if it could be as helpful for you as it was in our case.

Best regards!

ZhifangWang
Esri Regular Contributor

Thank you for helping us to figure out the workaround!