BA Configurator error (DTS Error)

Phenno
Phenno Member Posts: 630
edited 2006-06-11 in NAV/Navision Classic Client
Hi people.

For admins: Not sure should I ask about BA here or in some other mibuso subforum?

For ppl:
I'm having trouble with basic configurator execution. I followed steps properly, but configurator makes error and logs (in folder and in enterprise manager) says next:

DTS Package is: Post Process
Error is: An INSERT statement cannot contain a SELECT statement that assigns values to variable

In enterprise manager I tried to open design of that package but it gives me another error saying:
Error source: Microsoft Data Transformation Service (DTS) Package
Error descriptio: Invalid class string

Navision db is 4.01 (Native)
SQL Server is 2000 SP4
Win2k3 Server

Everything is done on same machine.


In logs, I can see that he properly executed to previous DTS-s but halts on this third one.

Comments

  • Phenno
    Phenno Member Posts: 630
    Actually, I Can open DTS package in design view but only from that machine.
    If I try to open it with Enterprise Manager from different machine it gives me back that "Invalid class string error"
  • Phenno
    Phenno Member Posts: 630
    I found out that Configurator creates package task that cannot be even parsed properly (with same message as an first error) so it could be a bug or my configuration error but don't know where.

    That task was for some date calculation for date dimension (but not for posting date). I skipped that and run configurator again.
  • Phenno
    Phenno Member Posts: 630
    hm... as I skipped that dimension it processed cubes ok and I'm working on BA properly.
  • kine
    kine Member Posts: 12,562
    There are sometimes probems with the dimensions. Do not forget, that you can use just dimensions connected to the base fact table (see known install issues)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Phenno
    Phenno Member Posts: 630
    I talked about dimensions in Cubes, not regular navision Dimensions (just to clear it up... :))

    You say that I cannot connect two tables (example, Customer and Territory) if there is no territory code in fact table?

    hm.. than it's quite a problem to make senseble cube without messinn up on fact tables...
  • kine
    kine Member Posts: 12,562
    You can connect that as related tabls, but not as dimensions. Better is to read the document with the Known install issues. Of course, you can create the cube manually, but it seems that the algorythm for the BA Basic in Navision has some bugs (it is not easy to create some universal code to generate the cube... :-))
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Phenno
    Phenno Member Posts: 630
    kine wrote:
    You can connect that as related tabls, but not as dimensions. Better is to read the document with the Known install issues. Of course, you can create the cube manually, but it seems that the algorythm for the BA Basic in Navision has some bugs (it is not easy to create some universal code to generate the cube... :-))


    buggy, buggy...
    do you (anyones opinion) prefer BA or some other solutions like Panorama or Cognos?

Categories