GateKeeper died

[system]

@Dave Rathbun

How “clean” was your upgrade? Did you deinstall, clean registry, reboot, reinstall? I know that’s not always required with some of the later versions, but it’s still a fall-back routine if something doesn’t seem clean in the upgraded environment. At least for me.

initially no, just upgraded (trying to preserve our AF environment on the same server). After that failed, Yep, Uninstalled/Deleted Directories/Pruned Registry … Same result

@Dave Rathbun

That sure sounds like a permissions issue. Or a problem with the way that the Webi app got registered with the DCOM service. Remember that the fact that the login screen is displayed is only an indication that IIS is up and running, there aren’t any Webi services required to build that screen. It’s not until you actually try to log on that any WI services are actually called.

Yep, spending a lot of time checking things in DCOMCNFG … An interesting thing is that we have an SDK application on the same server and it logs in ok, doesn’t run reports correctly, but it does authenticate … so it gets farther than the big blue button

@Dave Rathbun

Did any of those change during the upgrade? That you know of? Was IIS upgraded at the same time?

No, IIS wasn’t upgraded, but my thinking at this point is something was locked down in our IIS environment. Security Risks are very visable these days. I’m thinking this used to work, so they’ve either locked down something in IIS or removed some rights from my install id.

BOB’s been a wonderful resource thru this. I especially like this post from JodieS … Going back and double checking a few of these today.

---

Chris Pohl (BOB member since 2002-06-18)