BA Problem

vyanku

I found problem in BA with SP2 and SP3
When I try to start configurator it shows me error like
"Simba][SimbaEngine ODBC Driver][DRM File Labrary]No such daabase.
Anybody who try this type of combination?
Please suggest.

Where on SP1 when i try to run BA Advance Configurator it shows me error "Unable to restart ANT server"
Any one who suscessfullyy implement the BA whiout this error Please suggest .. [-o<

vyanku

Sorry for double post.

vyanku

Is SP2 is not support to SQL 2005 for Business analytics.?

kine

Yes, SQL 2005 for BA is supported in SP3. But just the basic part, not advanced!

vyanku

But for basic is there any other file required to run the configurator in Sp2?
Because When i try to run configurator from navision I got error like
" Error querying SQL Server "

What can I do?
Please

kine

You need to have new BAConfigurator which is used to generate the cube on MS SQL 2005. I do not know if there were some changes in NAV objects which will be connected to that (changes in XML structure etc.), but the .exe file is created from scratch with new design and new functionality for the MS SQL 2005...

vyanku

but the .exe file is created from scratch with new design and new functionality for the MS SQL 2005...

What do u mean by .exe file is created from scratch ....?

kine

That in SP3, is old BAConfigurator.exe for MS SQL 2000 working as in previous version, but for MS SQL 2005 there is new Configurator.exe created in visual studio, with new UI look (like when you are insalling MS SQL 2005 - the green circles with checks, red with cross, marking correctly finished steps or errors etc.). It means, this .exe is totaly new special configurator for MS SQL 2005...

vyanku

But I got the error when I try to run Configurator in SP2 with SQL 2000
as "Simba][SimbaEngine ODBC Driver][DRM File Labrary]No such daabase"

Anybody face this type of problem?
Please help

vyanku

Hi all
I found the solution for the above problem
When we install BA Basic and BA advance it created default drivers in NODBC . where the net connection is tcps and that is the problem and BUG of NODBC with BA. When we change that tcps to tcp the problem is solved .
But if we want to try this again it again gets converted into tcps so I think it is a BUG in NAV