Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Plannig - Analyst macro

Status
Not open for further replies.
Oct 30, 2003
7
HU
Macro:

@ODBCConnect("mssqldbname";"uid=sa; pwd=sa")
@Publish(12 cubes selected; Database is...; "01000001111";1)
@ODBCClose()

When I run this macro with CepBatch I got this error msg in the log file:

9999 Initialisation Failed
2005-08-02 15:02:08 Session Started
2005-08-02 15:02:08 An error happened when trying to log on to Analyst via Access Manager namespace default. Error was: The signon is invalid. Please check that Access Manager is properly configured on this client.
2005-08-02 15:02:08 Return code set to 9999 Initialisation Failed

I don't understand this error. I have a good odbc system dsn via msql db.
I've a database with signon in access man. with this odbc link. When I test the connections manually everything's good. When I use publish from wizard with same odbc link, everything's good.
What's the problem with macro? Anyone has come accross this problem and solved?

Laszlo
 
Laszlo,

Where is the authentication for the Cognos envirnoment(analyst) in your code? You can not do any actions in the cognos envirnoment unless you are known there as an userclass with sufficient rights...

add a piece of code to authenticate yourself in this script before you run your existing code. Samples can be found in this forum.

christenhusz
 
Hi, thanks for answer. Of course, first I logined in access manager as a member of root user class, and i have access a database definition (same odbc conn what the wizard used) with signon.

Is it needed an extra authentication in macro code if i have an active login?

Laszlo
 

So you did include the @AccessManagerLogon macro command as the first step?

Christenhusz
 
Yes in the Bi software you normally first login and then you open the the secured report,portal or cube. The macro is started as a new instance and therefore must be authenticated for the cognos envirnoment.

christenhusz
 
OK, I found this @AccessManagerLogon procedure and put in my code as first step. I logged out & close all the cognos programs, common logon server too. Then I run the CepBatch from command prompt.
After running, i see in the log file login & odbcconnet are good, but the publish...

9999 Application Error Logged as # 20: RANK ERROR
2005-08-03 16:09:59 Session Started
2005-08-03 16:10:03 Executing AutoStart Macro Tervezés Közös.Publish_FL
2005-08-03 16:10:03 User logged on successfully
2005-08-03 16:10:04 Executing macro step #1.
2005-08-03 16:10:05 0000 Error-free
2005-08-03 16:10:05 Executing macro step #2.
2005-08-03 16:10:05 Connection to ktrvir_riport established
2005-08-03 16:10:05 0000 Error-free
2005-08-03 16:10:05 Executing macro step #3.
2005-08-03 16:10:05 Return code set to 9999 Application Error Logged as # 20: RANK ERROR
 
I reindexed the model and tried again. No error msg in the log, but nothing's happened. Try the publish from wizard (same dcube, same odbcconnection, same mssql db), it works completely well, but from macro not. Why?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top