Impromptu error codes

[LaoDe]

Any body out there can tell me how to identify the meaning behind an Impromptu error No. like 1003 ?

There is nothing to find about in online help or elsewhere !

thanks for any tip L.D.

 

[iguanadon]

I'm new to the board, but saw this question and thought I'd just jump in. I assume that when you get that message, you're running a macro?

If so, I ran into that problem especially when upgrading from 4.0 to 6.0. It's one of two things I believe. In your macro in the Open Catalog statements, a userclass must be hardcoded in, and it must be one that is accessible by the user version of Impromptu. You can't just leave it as " " either. Also I found that 6.0 does not like Close Catalog statements, and must have an Open Catalog statement for each catalog. 4.0 wasn't as particular about that.

Hope one of these two things helps.

Scott

 

[CognosProfessional]

"Error 1003 error exception not handled by program"

Solution:
The macro populated the common log on server with user id, password and user class when opening the secured model. The user that was specified in the macro had ossignons set up as well, which would eliminate the need to supply the macro with the user id, password and user class. Because both were being used the macro was failing with the above error message.
To resolve the issue, either remove the ossingons for the user in access manager, or remove the log on information from the macro.

-or-

Impadmin.exe hangs if a secured catalog is used:
Error code:-1003
Error exception: error not handled by program

-or-

Error code: -1003 "ERROR exception not handled by program.

when running a macro from Scheduler.

A batch file will execute the macro manually and run correctly.


Solution Description

Confirm there are no other versions of Impromptu on the PC. If there is, the wrong version may be inadvertently called by the macro.

To resolve this issue remove all other instances of Impromptu. It is also possible to resolve this issue by editing the registry.


In order to fix this issue, you must edit the Registry and restart the computer.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft doesn't guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. If you wish to proceed, do the following:

Find associated keys from HKEY_Classes_root and find the corresponding application and ensure it is pointing to the correct location in relation to the active version of Impromptu.

-or-

Error 1003 occurs when the Impromptu application is not open and the scheduler invokes a macro to close that application.

In some cases, the application will be open but still the Error 1003 is displayed. This happens when more than one instance of Impromptu is open and these applications are being attempted to be closed in recurring task using scheduler.

For example:

An instance of Impromptu Application is opened at 10:00 AM and then another instance of Impromptu is opened at 10:30 AM using scheduler. Now the scheduler is being used to close these Impromptu Applications using scheduler recurring task at 11:00 AM and at 11:30 AM. The first instance will be closed by the task at 11:00 AM. However, when the second task is triggered at 11:30, it will cause Error 1003 because at this time the scheduler assumes that the Impromptu application has already been closed and there is no Impromptu application to be closed.

To solve this problem the recurring tasks should be set in the scheduler by alternating between the opening of Impromptu application and then closing the application. Or, by simply closing the Impromptu application in the first macro call.

Could be one of many things, but the above items are most common. You have what version?

CP