1

Hi guys, we have a second app being deployed on premise (very similar to first - another product) and we easily added the app to the console and tested it locally. All good so far! Then we've added the website to the IIS (8) and followed as much as possible the instructions in the documentation. We've accessed the app using the server or IP address and assigned port number and it all seemed good. We can see the login page, but the credentials we've created when testing locally kept not being accepted. We've decided to enter credentials from the first app, and voilà... we logged in, onto the first app?!! Some options are available (where entities have the same name) and data is in some tables where we've not added any data to the second app. So, we've established a correct access to second app when accessing it locally on the server (e.g. localhost:8082). When accessing from a network machine (e.g. servername:82) we get the correct second app login page, but then we see the data and menus from first app. We've stopped the first app on IIS and the result was the same, so it seems that the second app somehow is accessing the first app DB when we plugged in the website to IIS. Has anyone seen this behaviour before? I'm sure we are missing something on the IIS side of things as when we access the app locally we access the correct db for the second app. We've double checked the db settings and all good, so some redirect in IIS that is not correct?! Before anyone asks, the DBs have very different names, but do reside in the same DBMS SQL Server. Nothing unusual about that. LR.

asked 2016-02-17

1 answers