You need to find out if this was caused by a customization, or if it is
standard AX. If it is Standard AX report to Microsoft. I suspect someone
added custom code; there is a method designated to run on client. If the job
runs batch (server side) that will happen. The method or class needs to be
Ok - this error is driving me nuts. I do the following whenever I see
an order that has the Error Message The server-side impersonated
(RunAs) session tried to invoice a method that is available for
client-side processing only
1. Select the line
2. Select View Message
3.
PROTECTED] wrote:
From: Naeem Sarwar [EMAIL PROTECTED]
Subject: Re: [Axapta-Knowledge-Village] AX Error
To: Axapta-Knowledge-Village@yahoogroups.com
Date: Wednesday, 3 December, 2008, 4:08 PM
I synchronized the system it solved the problem. Bank accounts were required
to be reconfigured
I synchronized the system it solved the problem. Bank accounts were
required to be reconfigured!
On Wed, Dec 3, 2008 at 12:13 AM, MaryAnn Hand [EMAIL PROTECTED]wrote:
If the number sequence is ok, then there must be some customization
which is wiping out the journal number for the records
to MS with screenshot.
They will revert back with the Knowledge Base article
Regards
Abhishek Mehta,
--- On Tue, 12/2/08, MaryAnn Hand [EMAIL PROTECTED] wrote:
From: MaryAnn Hand [EMAIL PROTECTED]
Subject: Re: [Axapta-Knowledge-Village] AX Error
To: Axapta-Knowledge-Village@yahoogroups.com
Date
The error indicates that there is no journal number. Run the Number
sequence wizard - you need to have journal numbers to post!
On Tue, Dec 2, 2008 at 10:48 AM, Naeem Sarwar [EMAIL PROTECTED] wrote:
We are facing the attached error and the scenario is given below
The windows of AOS was
the numbers are being generated. for JV and lines it wont give error while
entering the data but during validation and posting.
do you think i still needs to check it... we haven't changed anything is
system the only thing changed it re-installation of AOS
On Tue, Dec 2, 2008 at 7:38 PM,
If the number sequence is ok, then there must be some customization
which is wiping out the journal number for the records that give
errors. I guess it is something you need to have a developer check by
debugging.
On Tue, Dec 2, 2008 at 12:06 PM, Naeem Sarwar [EMAIL PROTECTED] wrote:
the numbers
8 matches
Mail list logo