Hi Harish
Well that looks very
strange. Did you copy the application to another machine and it worked?. If so
you have a security problem accessing your application files. Sometimes some
clients can lock the files too hard. A solution for this is to change the
registry on the fileserver. Look below. Are your files write protected?
I
received a hint, because he read my request in the Technet about this problem.
He told me to take a look at the article Q296264.
http://support.microsoft.com/default.aspx?scid=kb;en-us;296264
We only changed this registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (Enabled by Default)
We put in 0.
Med venlig
hilsen / Best regards
Kim
Truelsen
EMEA GTSC MBS
Specialist Engineer
Microsoft Denmark
Tuborg Boulevard 12
DK-2900 Hellerup
Phone + 45 44 89 01 00
Mobile + 45 29 49 99 58
mailto:[EMAIL PROTECTED]
From:
Harish Mohanbabu
[mailto:[EMAIL PROTECTED]
Sent: 11.
februar 2004 15:26
To: [EMAIL PROTECTED]
Subject: [development-axapta] Re:
Microsoft - please help ...
Hi Kim,
Thank you very much for your assistance.
But my problem is different - as soon as I enter
user credentials to
the client, the application just hangs.
When I try to connect the client that is installed
in the same
machine as the application, the client just hangs
until we manually
have to kill the client.
But if I do it other way around, the client works
fine. That is if I
connect the client that is installed in our
application server to
another instance of application (in a different
machine) the client
works absolutely fine.
Do I have to remove the application from the
application server?
Please advise.
Thanks,
Harish
--- In [EMAIL PROTECTED],
"Kim Truelsen \(MICROSOFT
BUSINESS SOLUTIONS\)" <[EMAIL PROTECTED]>
wrote:
> Maybe your problem is this
>
>
>
> Med venlig hilsen / Best regards
>
> Kim Truelsen
>
> EMEA GTSC MBS
>
> Specialist Engineer
>
>
>
> Microsoft Denmark
>
> Tuborg Boulevard 12
>
> DK-2900 Hellerup
>
>
>
> Phone + 45 44 89 01 00
>
> Mobile + 45 29 49 99 58
>
> mailto:[EMAIL PROTECTED]
>
>
>
>
>
> ________________________________
>
> From: Harish Mohanbabu
[mailto:[EMAIL PROTECTED]
> Sent: 11. februar 2004 11:17
> To: [EMAIL PROTECTED]
> Subject: [development-axapta] Re: Microsoft -
please help ...
>
>
>
> Hi,
>
> Thank you all for your kind responses.
After seeing your replies,
I
> tried the following -
>
> 1. Copied Axsys.aod from a running
installation to this
installation
>
> 2. Also copied Axsys.aod under Old directory
to the problematic
> installation
>
> 3. Also rebuilded the .aoi file.
>
> Earlier on, I tried this as well - I removed
the Axsys.aod from
the
> directory and let the system rebuild this
file. But the size of
new
> Axsys.aod is around 18 KB where as the old
Axsys.aod was around
165
> MB. Then Axapta lets me log in to the system.
But I am unable to
see
> all the modules including the 'Administrator'
menu.
>
> Till now, I have absolutely no idea as to
what could be
wrong .....
>
> Thanks,
>
> Harish M
>
>
> --- In [EMAIL PROTECTED],
"Gert Neetesonne"
> <[EMAIL PROTECTED]> wrote:
> > Just copy axsys.aod from your test
version of from your local
> installation
> > to the live version.
> > This file is the same for each major
version of Axapta (in your
> case 3.0)
> >
> > Gert Neetesonne
> > Edan Business Software
> >
> >
> >
> >
> > >From: "Preston A. Larimer"
<[EMAIL PROTECTED]>
> > >Reply-To: [EMAIL PROTECTED])
> > >To: <[EMAIL PROTECTED]>
> > >Subject: RE: [development-axapta]
Microsoft - please help ...
> > >Date: Tue, 10 Feb 2004 14:28:10
-0500
> > >
> > >Have you tried rebuilding the
Application Object Index?
> > >
> > >If you dont know how... find the
file in the application
> directory with
> > >the extension .aoi and rename it,
you can delete it later if it
> fixes
> > >your problem, then restart axapta
you should get a message about
> > >rebuilding the indexes.
> > >
> > >-Preston
> > >
> > >
> > >
> > >-----Original Message-----
> > >From: Harish Mohanbabu
[mailto:[EMAIL PROTECTED]
> > >Sent: Tuesday, February 10, 2004
1:59 PM
> > >To: [EMAIL PROTECTED]
> > >Subject: [development-axapta]
Microsoft - please help ...
> > >
> > >
> > >This problem is still
persisting. Can someone help me
please ...
> > >
> > >Regards,
> > >
> > >Harish
> > >
> > >--- In [EMAIL PROTECTED],
"Harish Mohanbabu"
> > ><[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > Has anyone come across this
error message before?
> > > >
> > > >
----------------------------------------------
> > > > The file 'axsys.aod' does not
contain the correct digits.
> This is
> > > > normally caused by file errors
or by mixing different
> application
> > > > versions. A back up of
correct files should be restored to
> avoid
> > > > further damage.
> > > >
> > > > Navision Axapta cannot be
executed.
> > > > ----------------------------------------------
> > > >
> > > > Environment - Axapta ver 3.0 +
SP2 with MS SQL Server 2000
as
> the
> > > > back end. Local users
connect as 2-tier clients while remote
> > >users
> > > > connect through Citrix.
> > > >
> > > > System was working fine till
last week. All of a sudden
while
> > > > trying to connect to Axapta,
one of the remote users got the
> error
> > > > message mentioned above.
Now none of the users are able to
> > >connect
> > > > to Axapta.
> > > >
> > > > Can someone help me please
....
> > > >
> > > > Regards,
> > > >
> > > > Harish
Yahoo! Groups Links
