IWR 7.0 BURSTIN PROBLEM 1

[benbotektips]

Oracle 8i, IWR 7.0

Can someone explain in explicit detail what needs to be done in Access Manager, Report Administrator, and Upfront, to successfully burst to select users? I have a catalog with user profiles, reports off the catalog, on the client they work fine. Publish to IWR intranet, as public reports the'yre fine. The problems come with bursting; once I check the box in Upfront, the reports don't burst and don't work anymore. I'm logged in to Upfront as administrator; administrator is a member of Root user; root user class in Upfront has read, write, execute access, and is the owner; the category 'all user classes' has no access, but the users to get the burst all have read access; the database in Access Manager is defined, with a valid signon; administrator has access to database with signon assigned [ex. sales(admin)], and administrator is a member of root user class and creator user class. In Report Administrator, the report set is defined with implicit user class mapping, a manual mapping for creator->Root user class, and the 'users' database signons are in Access Manger namespace' radio button is selected, with then database name underneath. When it bombs, this is the error:

The following error has occurred:

The report request failed.
Error: 0, Generic; Process ID: 4544; Thread: 4212; Host: ADSALESRPTS2; Text: Logon error while connecting the database.; BackTrace Info: 1. File Name: Y:\src\impromptu\ImpromptuServer\app.exe\ole.lib\APPAUTO.CPP; Line#:3545; Desc.:CAppAuto::ConnectDatabase;

 

[griffindm]

ben,

Can you check that all of your user classes have valid embedded database ID's and passwords? The error message seems to indicate a problem with at least one of them.

Regards,

Dave Griffin


The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
Want good answers? Read FAQ20-2863 first!

http://www.decisionsupportgroup.com

 

[benbotektips]

Dave,
Thanx 4 the reply. Do u mean, check (via the Impromptu client) all the user PROFILES in the catalog that was published, to see if each one to be bursted to in IWR has the database name & pw embedded, or check in Access Manager on my server, that each and every user CLASS to be bursted to has its database signon, access, and membership set? I'm logging on as administrator, bursting it to everyone else, are u saying the burst will fail if any of the users I'm bursting TO is not completely 'ready-for-primetime'? I had thought that would only be after trying to log in as one of the bursted classes, not also to burst. If true, then the way to go would be set up as couple of targeted users, then burst ONLY to them, right? If that's true, I would have to change security from the topmost folder level (the one that holds the 4 reports to be bursted), to give access one at a time as I fully prep each user class for read access. I hope I understand your point right.

 

[griffindm]

via the client, check that the user profiles has a valid database id and password. Sorry for the confusion. In the Catalog | User Profiles they are called profiles. In many other areas of the product, including the catalog login screen, they are called classes.

Dave Griffin


The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
Want good answers? Read FAQ20-2863 first!

http://www.decisionsupportgroup.com

 

[benbotektips]

Dave,
Thanx for your help with this. Your suggestion got me onto the track of finding the source of the problem. The problem is fixed, it turned out to be a combination of 2 things.
First, the relationship of access rights of administrator compared to other users is extremely confusing. In 6.0, we have administrator, defined as a user, belongs to root user class, database connection defined, signons embedded in catalog AND attached to user manager. To burst, I log onto report admin, schedule the burst immediately, and it burst to all users underneath a user class under root (let's call it 'managers'). Database logon access is assigned by user class, which in 6.0 means embedded in the catalog. In 7.0, you are not allowed to use catalog profiles (what 6.0 called 'user class') for database logon, you MUST use Access Manager, for bursting. This brings along problem 2. WHat I would do in 6.0 is logon to report admin as administrator, burst, then logon to the intranet with the same administrator id, and check the results of the bursted reports. Then, I would open up a second browser, logon as 'manager' (the user under 'root', with other targeted users under it), and check the reports again. When I did this in 7.0, I would get the 'logon fail' or 'user class not found' error, which made no sense since administrator is defined as a user, member of user class 'root', access to the rite database, etc. The problem was since we're forced to use Access Manager logon, there's no user profile named 'administrator' in the catalog, just creator. And therefore, it's trying to use implicit class mapping to find 'administrator' in the catalog. Subtle, and infuriating, as this is a radical change from 6.0. Problem was solved by adding a manual user class mapping for root user class <---> creator. Now, I log on in 7.0 as admin, burst to all other user classes with read access, and can run the report as admin after the successful burst. This is not 'logical' or 'intuitive', especially for an experienced 6.0 person using the existing setup as a model. It's an especially nasty 'gotcha'.

 

[Sherylj]

I can't seem to get a report to burst and this is the error message I get. Does this message mean anything to anyone? Attention

Unable to execute report C:\Test\Published\Infinium AR\apps\AR Yard Aging.imr. Reason: Error: 0, Generic; Process ID: 4180; Thread: 4212; Host: CFD2-MID-TX-001; Text: Unexpected Error in ExecuteRunReport. Please contact your System Administrator. Report: \\?\C:\Test\Published\Infinium AR\apps\AR Yard Aging.imr; BackTrace Info:.

 

[benbotektips]

Cognos' error messages are notoriously lacking, especially IWR. Check your server's event viewer, it may yield more useful error info, something specific like failing to map user class, prompt timeout, etc.
Also, which version IWR?