FM giving error messages after migration when selecting data sources

[fastf00d]

Hello all, this place has been so handy in the past I thought I'd come say hello again.

We've just migrated our Cognos server from 10.2.1 to 10.2.2 - right now we only have the 10.2.2 version so there's no going back. The migration itself has been pretty smooth but we have a problem getting FM up and running.

So far I've uninstalled the old version of FM, downloaded the corresponding version of FM to my machine and installed it. I've then checked the gateway and dispatch URI shown on the servers cognos configuration. These details have been copied into my local machine's cognos configuration so FM can function correctly.

The only change I had to make was with the dispatch URI. Instead of using:

http://mycognosaddress:9300/p2pd/servlet/dispatch

I ended up using:

http://mycognosaddress:9350/p2pd/servlet

Because this allowed me to see my data sources when setting up a new FM project. Note that I am not using previous projects I'm trying new projects every time to rule out the possibility of project issues. Whenever I use other combinations of the address I don't end up seeing my data sources.

Now here's where the big problem occurs once I am able to see my data sources once I select one I know is fully operational and try clicking next FM crashes and I then get the following error message:

BmtActionsHelper.cpp(488): CCLUnknownError: CCL_THROW:BmtActionsHelper::DoAction This application has encountered a non-recoverable error and is about to close. Please contact your System Administrator for assistance.

I've been trying to find a solution to the problem but haven't found anything that directly addresses this specific problem. The only hints I can gather is that there may be a problem with a different Namespace being used, Permissions on the Cognos server or that the data sources may include some self referencing data (which I can't see as they were working fine before).

Sorry for the wall of text but otherwise it wouldn't have made sense! If anyone can offer some help of clues as to what's wrong that would be so awesome and hopefully it may help someone else out in the future too, thanks!

[bus_pass_man]

I must say that you're taking the problem rather more phlegmatically than I would. 

After you uninstalled, did you clean up the left-over files?

Can you explain what you mean by '[t]hese details have been copied into my local machine's cognos configuration so FM can function correctly.'
I think you're saying you copied the server's configuration directory to your FM installation location.  Is that a correct understanding?  Why did you not just configure FM via its configuration tool? 

Why did you believe that you needed to change the dispatcher URI? Has the server administrator been monkeying around with settings?  What happens if you just changed the port to 9350?

Now here's where the big problem occurs once I am able to see my data sources once I select one I know is fully operational and try clicking next FM crashes and I then get the following error message:

I think you're saying that FM crashes when you're in the metadata import wizard.  Is that a correct understanding?

When you saved your settings, did you get a message about not being able to save it in encrypted format?

If you run FM as administrator, do you get the problem?

[fastf00d]

Thanks for replying bus_pass_man. The previous version of FM was in a completely different directory to this version of FM and I cannot see anything left of it so yeah it seems cleaned up to me.

The details I was referring to were the Gateway URI and the Dispatcher URI for external applications. No files were copied just the text which is displayed on the servers Cognos Configuration to my own PC's Cognos Configuration (so yeah I did use the tool). 

My administrator has told me that the port for the Dispatcher URI for external applications should be 9350 and it certainly seems like the address I have in there is correct. Finally I have run FM and the Cognos Connection tool in Administrator mode and have had no change in the results.

I just tried creating a new data source to see if that could work around the problem but it gives me the same error. What does that error code mean in this situation though? We'll keep at it but this is feeling a lot more complicated than it should be, any help you can leave would be awesome.

[bus_pass_man]

More ideas:

Have you tried testing something which already exists in an existing model?

Do you belong to a role which has the can import relational metadata capability?  I wonder if the everyone role was assigned as a member of that capability and someone came along and decided to clean it up but did not add you, either directly or as a member of a role, to the capability.   That should not cause FM to crash but then again nothing should ever cause any application to crash.

Was anything changed in your data source connection?

When you saved your settings, did you get a message about not being able to save it in encrypted format?

I'm assuming that you were able to import metadata before.  Is that a correct understanding?

Is your new model in classic mode or dynamic mode?   Does your data source connection support whichever one you're using? Is the new model in a different mode?

If the data source connection is using dynamic mode, did the portal administrator put the necessary JDBC drivers in the correct spots? 

[MFGF]

Are you completely sure your version of FM ties up exactly with the version of the BI server? Has one of them been patched (ie a fix pack applied) and not the other?

MF.

[fastf00d]

Certainly lots of ideas from bus_pass_man - and you were the closest as I have now resolved the problem. After trying an existing project/model I discovered that was operating perfectly fine and I could publish more working packages with it. So it was a problem with new projects/models.

Eventually through trial and error I unchecked the 'Use Dynamic Query' checkbox that appears in the first dialog box that pops up. After that I was able to create a new project just like I had before the migration to the new version and have so far been able to perform all the usual functions too.

Hopefully that may help anyone else experiencing that particular problem. Thanks again again everyone :)