For planning 8.2 we're set up a network install for our analyst users. However when our user's launch analyst from their client machine they either get the "There was a problem logging on" error or this error
A Fatal Error has occurred in the startup section of the application.
The application will be terminated.
Please report the following information:
Function name: CompileProgIDTable
Namespace: #._OS
=======================
DOMAIN ERROR
CompileProgIDTable[17] 'text'OEWC'oleclient' 'EpBrandingHost.TextBrandingHost'
The web application works fine, it's just analyst clients we're having trouble with. Has anyone had similar issues and were able to resolve them? Any help would be appreciated. Thanks
For Planning Analyst did you open the cognos configuration on the client computer and check the settings and save the changes?
Yes, i changed and saved the configuration settings and checked to see if i can access the site using the gateway uri. We still can't connect to analyst.
There is a thread in Cognos knowledge base about that. Check if it helps.
http://support.cognos.com/knowledgebase/googlesearch?load_kb_document=1&dr=kb1&uniqueid=133874
<CUT>
Description:
Fatal application error when trying to open Planning - Analyst.
Error Message:
A Fatal Error has occurred in the startup section of the application.
The application will be terminated.
Please report the following information:
Function name: CompileProgIDTable
Namespace: #._OS
=======================
DOMAIN ERROR
CompileProgIDTable[17] 'text'OEWC'oleclient' 'EpBrandingHost.TextBrandingHost'
Solution:
For versions prior to 8.2: Start Configuration Manager, and do an Apply at the Cognos Planning level.
For version 8.2: Run the command x:\program files\cognos\c8\bin\epophost.exe /regserver
</CUT>
The analyst users have local administrative rights to their machines? Pre-8.2, this was true, not sure if it's changed as a requirement for 8.2/8.3 but I would guess not.
jan.herout, we're running 8.2 and i tried the opophost script and i didn't solve the problem.
SomeClown, I didn't know about the admin rights requirement. most of our user are not local admin but would take an act of congress to allow it. i'll test with some people who are admins and see if that corrects the problem. Thanks
Actually, you don't need to have Local Administrator privileges for RUNNING Analyst (however you need it for installation).
Are you sure you have everything configured properly? Under environment :
- Gateway URI points to the server
- Dispatcher URI points to the server
- Content manager URIs point to the server
Do you receive the error BEFORE the user has opportunity to input crendentials, or AFTER the user inputs their credentials?
we checked and doublechecked the credentials. we receive the error before the user has opportunity to input crendentials.
OK, I am not able to tell what exactly problem is, but this is what I would do in your shoes:
(1) CHECK CONFIGURATION ON CLIENT SIDE - you probably did several times.
(2) CHECK LOG FILES ON SERVER FOR PROBLEMS
http://support.cognos.com/opendocs/en/html/planning/8.2/contrib_admin_id19356_Toc19961462.html
Check especially planningerrorlog.csv for errors. It should help.
(3) CHECK CONFIGURATION ON SERVER ONE MORE TIME
I vaguely remember to face similar problem once. Symptoms were very similar - working Cognos Connection and "dead" Analyst. Now, if my memory serves me well, problem was on SERVER side, not on Analyst side. Sorry that I am unable to remember exactly what that was... Check that under Environment, you do not use LOCALHOST in any part of the configuration, but full server name insted.
My bet is that after studying log, you will know better what is the source of the problem.
Someone more experienced than me should help...
Seems to be two kinds of errors. One appears to be install-related: I've seen those kinds of errors in earlier releases when the users were not admins and tried to install the software. The registry entries don't get completed (missing CLSIDs, etc, etc) so you get weird errors like that.
If they were not local administrator to their machine, Analyst probably won't successfully install (it'll tag as complete, and make you think it finished successfully, but it didn't). If the endusers don't have local admin rights, you need to come up with an alternate install method (SMS, desktop support staff, etc)
Not sure if that would also clear up the credential error.
Someclown, our client installs are handled by msi installers through the add/remove programs list. In our enviroment all software have to be approved before users can use them, once approved the help desk place the msi's there for our end users to add.
jan.herout, i'll take a look at the server logs and check the configurations on the server. we didn't use localhost, but it could be something else that was minor that we didn't notice before.
thanks for all the assistance.
Solved the issue. There were two problems.
1. The MS SOAP toolkit didn't get installed completely with the client install
2. The end users had to map the Analyst Shared location and choose the reconnect at logon.
After both steps are complete the application works fine.