cancel
Showing results for 
Search instead for 
Did you mean: 

Web Application Management Console

Valeria_Burian
Champ in-the-making
Champ in-the-making

Trying to run Web Application Management Console and receive the following error message:

"Unable to load web application"
Any troubleshooting hints?

Thank you

1 ACCEPTED ANSWER

Pawel_Czopowik
Champ on-the-rise
Champ on-the-rise

I ran into the same problem and with the help of Findley on team M, we were able to resolve this. The problem is with the bindings in IIS for the website/app. 

You must have the HTTP or HTTPS binding as the first binding above the other defaults (net.tcp, net.pipe, etc). You can simply remove them and re-add them in the right order (take a screen shot before hand so you an put in the other bindings 🙂 ). Alternatively, if you know what you're doing, you can also edit the  %WINDIR%\System32\inetsrv\config\applicationHost.config file. Just make a backup first!

I tested this with HTTP & HTTPS bindings as well as just HTTPS and it worked for me. I did not need to reset IIS.

Thanks,
Paul 

View answer in original post

5 REPLIES 5

Seth_Yantiss
Star Collaborator
Star Collaborator

[quote user="Valeria"]Any troubleshooting hints?

First tip: Include the version of OnBase, the version of the OS you're running the software on.

Question: Have you tried to Uninstall / Reinstall the Web Management Console?

Cheers,
Seth

Valeria_Burian
Champ in-the-making
Champ in-the-making

Seth,

 

Web Application Management Console version is 12.0.1.128

I am running it from the app server Win 2008 R2.

Yes, I did try uninstall and reinstall.

 

Thank you

Not applicable

Hi Valeria,

Thanks for using the Community Forums!

When you receive this error, does it occur immediately after you launch the Web Application Management Console (WAMCon), or does it occur after you choose either AppNet or AppServer to configure?

Thank you,
Andy Gonzalez

Pawel_Czopowik
Champ on-the-rise
Champ on-the-rise

I ran into the same problem and with the help of Findley on team M, we were able to resolve this. The problem is with the bindings in IIS for the website/app. 

You must have the HTTP or HTTPS binding as the first binding above the other defaults (net.tcp, net.pipe, etc). You can simply remove them and re-add them in the right order (take a screen shot before hand so you an put in the other bindings 🙂 ). Alternatively, if you know what you're doing, you can also edit the  %WINDIR%\System32\inetsrv\config\applicationHost.config file. Just make a backup first!

I tested this with HTTP & HTTPS bindings as well as just HTTPS and it worked for me. I did not need to reset IIS.

Thanks,
Paul