03-22-2023 01:08 PM - edited 03-22-2023 01:09 PM
Recent installation of 7.3.1.
1 WebServer and 3 AppServers.
When I log on to the WebServer and attempt to hit "http://localhost:50001/OneStreamWeb/OneStreamXF.aspx, I get an error that says 'Unable to access application server using address "http://[AppServer]:50002/OneStreamApp." '
If I open a browser on my webserver and navigate to http://[AppServer]:50002/OneStreamApp/svc/Data.svc, I get the expected result ("You have created a service").
I was also able to create an application database from my app server, so I know the connection to the db is correct.
How do I figure out what is missing?
Thank you in advance for any help.
03-23-2023 03:18 AM
Did you check in IIS that all the application pools have started?
Was it an upgrade what you did? Did you open your firewall ports? During testing time you could disable the firewall no?
After checking that, what I would suggest is that you go back to the OS Server Configuration and you redo all the install/upgrade steps where you assign the XFAppServerConfig and XFWebServerConfig. I mean the ASP and webserver config files.
03-23-2023 12:18 PM
Thank you for the reply.
Yes. All of the application pools have started. I also tried stopping them all and restarting them.
There are no firewall issues. I can ping all servers. If firewall was an issue, I wouldn't get "You have created a service" when I attempt to access OneStreamApp.
I don't want to reinstall OneStream.
Are there any logs that I can look at to determine where the issue is coming from?
I believe traffic should flow from OneStreamWeb, to OneStreamApp, to SQL Server.
Is there a way to test access to SQL Server from OneStreamWeb?
Is there a way to test access to SQL Server from OneStreamApp?
03-24-2023 04:01 AM
Sorry, I did not say to reinstall OneStream but only to review the pointers of the web.config files for each servers. Look at the extract from the Upgrade_Guide below. I would look into that direction.
Regarding the logs, if you look int the webconfig of the webserver you will see the option to activate WebServer detailed Error Logging. (True False)
03-24-2023 08:07 AM
Thank you for the reply. I have determined, since the error I was getting referenced the correct name of the AppServer, the ASP.Net Configuration file was setup correctly. I have not completely fixed the issue, but I am much closer. I changed the WebServer config file to point to a single AppServer to perform all functions. This got me passed the error, but I ran into another problem. I may have to create a new post for that issue. Once that issue is resolved, I will figure out how to get the other AppServers back in the game. I will post when I am done.
03-28-2023 01:07 PM
Each time I think I am getting close, I run into another problem.
I still believe the problem is with permissions.
Currently, when I attempt to access :50001/OneStreamWeb/* the AppAppPool has a fatal communication error with the Windows Process Activation Service and shuts down.
Initially, I was using a service account that was created specifically for IIS. Now I am using "NETWORK SERVICE" to run the AppPools.
I'm getting closer but still cannot access OneStreamWeb
03-25-2023 03:37 AM
Nice job. That is exactly what i was pointing too ; The config files. Please keep us up to date! Good luck.
04-13-2023 09:29 AM - edited 04-13-2023 09:30 AM
I believe this was a permissions issue. When I changed the identity of the AppPool in IIS to a service account that was a little more "open", things worked properly.