When Axapta is running from a service or web app there isnt nessesary any current user and in that case Axapta cannot find the configuration information from HKEY_CURRENT_USER

If you copy the registry settings from HKEY_CURRENT_USER to
HKEY_LOCAL_MACHINE and remove the settings from HKEY_CURRENT_USER you can be sure that Axapta picks up the right configuration.

I can see that you already have registret the COM+ application under a specific user and that should take care of it, but just to make sure you should try it out.

If this doesnt help, you should try running the service under the same user account you are using for the COM+ application. Maybe it has something do with rights.
If your service act as a server as well and accept connections from the outside, you should be a little carefull by doing this from a security perspective.


-------------- Original message --------------
I know it can work, since as I said it works in my dev environment, but it
seems to be related to this machine. Could it have something to do with the
fact that the test machine first had axapta installed using web deployment,
then uninstalled then reinstalled locally?

I will try the registry edit. Could you tell me why this might have an
effect?

Regards,
Matt Benic
.Net/Axapta Analyst Developer
UTi Sun Couriers Division
Support the Xbox 360 in SA campaign
<http://forums.xbox.com/ShowPost.aspx?PostID=12592431>


-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: 02 June 2005 04:53 AM
To: [email protected]
Subject: Re: [development-axapta] COM file access error


I have done this as well and it worked, so it is possible to call the
business connector from a service.

Which user does your service run on?

You could try this. Copy the Navision registry key from HKEY_CURRENT_USER to
HKEY_LOCAL_MACHINE




-------------- Original message --------------
Hi all,
I have developed a windows service in C# that makes use of the ABC. It works
on my development environment, but on my test system, an exception is
generated by a call to IAxapta2.Logon2 with the following message:
{"File Error : The application files are not accessible. This can be caused
by another Navision Axapta instance using the application files in exclusive
mode.\n\nNavision Axapta cannot be executed. Please restart the Navision
Axapta Business Connector before logging on." }

A client on the test machine using the same configuration as the ABC starts
up successfully, so the current user definitely has access to the app and
bin files. The configuration is for a two-tier connection, and the ABC
component (registered on COM+) is definitely running under the local user
account (ie the same account that the client would use to access the files).

Does anyone have any suggestions?
Regards,

Matt Benic
.Net/Axapta Analyst Developer
UTi Sun Couriers Division

Support the Xbox 360 in SA campaign







Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/

To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

[Non-text portions of this message have been removed]






Yahoo! Groups Links













Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
 
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
 
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

[Non-text portions of this message have been removed]






Yahoo! Groups Links

Reply via email to