All macros fail when executing from either Analyst or epmacroexecutor command line.
Macros remain in queued state.
EP Install: 10.1.6235
Windows 2008 R2 64 Bit (server)
Windows 7 (client - user workstation)
Oracle 10G version 10.1.0.3.0 DB Server
Diagnosing the problem
Oracle 11g client tools installed on the user workstation.
Users are members of PRA and Server Admins Groups in Cognos Connection.
Verified that user has full control on c:\Program
Files(x86)\ibm\cognos\c10 directory on c: drive and also registry.
Cognos services account executes Cognos services on Planning Server.
Network id is located in Active Directory and is used for single sign on.
From the users workstation, opened Analyst and select tools->options
Confirmed that the path to filesys.ini is the same path that the server
is pointing to (\\servershare\Cognos\EP\Analyst\Filesys.ini)
Confirmed that the user has full rights to the library folder in Windows
explorer on the Cognos server.
Confirmed that from the user workstation, from Analyst, user can
manually run the individual steps that are in the macro. No pop up
messages occurred to enter credentials.
As a test, user created a simple macro and added the step dcube open and
executed the new macro. The error still persists.
User created a a very basic library and saved it to the local C:\ drive.
Created a few dlists and new dcube in the new library.
Created a new macro in this new library and executed the new macro. The error still persists.
Resolving the problem
In 10.1.1 if jobs and macros remain in queued state, it is because
the Planning Administrator Console service needs to run on the same machine as
the monitor and agent services. These services are installed with BI but not with the separate Planning server installation kit. Workaround: Use the Planning complete kit and select Planning Admin console service. The monitor and agent services will be installed.
In addition, in order for macros to execute, the planning Job Service needs to be
installed on the same machine as the Planning Administration Console
service. It can be disabled in the Planning - Administrator, however, it does need to exist.