Thanks Jeff. We actually just got version 1.1 installed and working properly this morning. We had to implement three separate workarounds, but did get it working.
We downloaded the configure.dtd file and hosted it internally and used a hosts file entry to point the server to it.
Then we had to make a modification to this file in order to get the database to upgrade:
A minor update to the SCA installer was released today. The Deploy Installer wizard on the SCA dashboard in the TEM console will now deploy SCA 1.1.7, which resolves the issue some of you were encountering in the install process.
If SCA is currently installed in your environment, you don’t need to take any action.
I´m trying SCA. I´ve just installed it and everything was going ok: graphs, computers groups, users, overview…I added the webreports database and the primary database. Everything is in localhost. SCA did the first “mandatory import”, but now when I try to open the “import tab”, inside of “management tab” it appears "We’re sorry, but something went wrong.
Please contact your Tivoli Endpoint Manager Analytics administrator if the problem persists."
I restarted all the services related with TEM but still the same.
What do you thing about this issue? Where could be the problem?
Sounds like something might have gotten out-of-sync between the License Overview dashboard and the console itself. Can you verify that “SCM Reporting” does (or does not) appear in the following views:
(1) Select “Bigfix Management” domain buttom -> expand the “Manage Sites” node -> expand the “External Sites” node -> check whether “SCM Reporting” is in the list under “External Sites”
(2) Select “All Content” domain button -> expand the “Sites” node -> expand the “External Sites” node -> check whether “SCM Reporting” is in the list under “External Sites”
If you do NOT see SCM Reporting under either of these nodes, then something probably went wrong in the License Overview dashboard, and my advice (if you haven’t already done so) would be simply to restart the console and try again from the License Overview. However, if you do see SCM Reporting in one or both of these views, the most likely explanation is that for some reason, the site hasn’t gathered the latest content yet (you can verify this by clicking the SCM Reporting node, and checking the “Current Version” on the “Details” tab. If the version is still 0, you’re out-of-date). If this is the case, the next step would be to verify that your “BES GatherDB” service is running on the BES Server. Give this a try, and please let me know if you’re still have trouble.