Problems with C/Front SP3

KappeKappe Member Posts: 64
Hi

I have a problem with the new SP3 C/Front.
We have a ASP page working with a C/Front component.
When I now upgrade to the new SP3 C/Front it stops working :?

I tried lots of things within the last days but I couldn't solve it, so hopefully someone here has a good hint for me.

So here are my "test"-results... I would call it playing around :whistle:

I have tested it on several machines and this is the environment of my local one:
SP3 Client + SP3 SDK + SP3 Database Server (All from W1 CD)

SP3 Database is running local within the SP3 Database Server
and
a copy of the SP3 Database is running within a SP3 Database Server on a Server within the network.

I can connect with my local Client to both databases without problems.

We have a setup function for our ASP page.
Here we can set/select:

- C/Front Servertype (SQL/Native)
- Servername
- Authenticationtype
- C/Front Path (Version independable :-k )
- Company Name

1) When I set up the first points and then try to select the company name, I got the following error message:

C/Front Fatal Error: cfront.dll or cfrontsql.dll is not loaded.

I have installed everything new, but I keep this message. Within the SP1 environment it works!

2) After that I thought: OK, then try the sample.exe with the C/Front folder.
When I run this, I got the errors 203 and 142!
These belong to the Date and Time functions within the sample.
The sample calls the English date and time functions but my German Windows XP can't solve that.
This looks like a wrong "language layer"... :-k
for example: t(oday) <> h(eute)

3) So I started the next step and compiled the DotNetSample application.
This worked fine until I started it.

a) The testdatatypes function throws
an unhandled exeption - I think it is the same then in the sample.exe (Date&Time).
And then it is becomming advanced:

b) When I try to connect to my local database server I got the message that it is not in my hosts file.
Why? The client can connect. (If this is handled within the .Net code then sorry - this I haven't check)

c) When I try then to connect to the database server within the network (which is in the hosts file) I get the message:
The Navision CFront initialization failed.

So perhaps anyone here can give me a hint. I don't have a clue where to search now. Or is it just my environment which is causing the errors?

Thanks in advance for your help!

Regards
Kappe
___________________________________________

Kappe

Comments

  • kinekine Member Posts: 12,562
    May be you can ask Microsoft, if you are partner... :?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • KappeKappe Member Posts: 64
    Thanks for your answer kine.

    I'll finish my testing today.
    Maybe I must search the error in another part of the system :-k

    But if this all don't solve the problem I will contact MS.

    //Kappe
    ___________________________________________

    Kappe
  • SabbySabby Member Posts: 8
    Hi Kappe,

    We've installed the SDK SP3 and we have the same errors you got. Do you remember what was your solution?

    Thanks,
    Sébastien Aussant
    Bath Fitter
  • kinekine Member Posts: 12,562
    I can just add some experiences with SP3 C/Front I have now:

    1) Best is to have installed full client on the PC
    2) Set the client path when initializing C/Front to this installed client
    3) Check, that the liense laguage code is same as language code in fin.stx in the client folder
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • KappeKappe Member Posts: 64
    Hi Sébastien

    Sorry for my delay - just saw your posting.
    Seems I removed the email notification for this post.

    Currently we don't have "the solution" for this issue.
    Because we have decided to discontinue this product.
    BUT if we have to install it at existing clients we go this way:

    If SQL database we install SP3 and it works.
    If Native database we install SP3 and replace the C/Side files with the ones from SP2 - works in our case.

    Not very "generic" or nice, but in general we can live now with this "feature". :whistle:

    Regards
    Kappe
    ___________________________________________

    Kappe
  • SabbySabby Member Posts: 8
    Hi Kappe,

    Thanks for your reply. We also had to do something not very "generic". We had this problem with SP3 Update 6.

    What I did is I installed SP3 client with SDK SP3 Update 6 and it worked! Very strange but it worked!

    Thanks again wit your help.
    Sébastien Aussant
    Bath Fitter
Sign In or Register to comment.