You can upgrade directly to 3.0 SP4 from 2.5.  Number sequence references in 3.0 must be unique.  A number sequence can only be used once.  You need to clean up number sequence references in 2.5 before the upgrade.  It's one of those architectural changes they don't tell you about.

Jim Chwaszczewski
[EMAIL PROTECTED]

________________________________________________________________________

Message: 1        
   Date: Fri, 10 Mar 2006 14:48:34 +0100
   From: "Dahlsgaard Jan" <[EMAIL PROTECTED]>
Subject: SV: Error whil upgrad Ax 2.5 DB to Ax 3.0 SP4

I don't think you can go directly from 2.5 to 3.0SP4. You have to upgrade your db to 3.0 og 3.0SP1 first.

________________________________

Fra: [email protected] [mailto:[EMAIL PROTECTED] På vegne af pbercher
Sendt: 10. marts 2006 13:29
Til: [email protected]
Emne: [development-axapta] Error whil upgrad Ax 2.5 DB to Ax 3.0 SP4


Hi,
during the upgrade process i get the folowoning message:

***
Info      Message (13:26:31)      Run job 'updateCustSalesLinkTable'
ordered by 'Admin' in database 'pa1'.
Error      Message (13:26:31)\Table CustPickingListSalesLink
      Reference for call of number sequences is not specified.
***

any good hints where to look?
Thx
Pirmin --------------------------------------------------------

The content of this e-mail and any attached files is confidential, and may be subject
to certain privilege.  This e-mail is intended for the designated recipient(s) only. 
If you have received this e-mail in error, please immediately contact the sender.

Pursuant to Treasury Circular 230, the IRS requires us to advise you that if this e-mail (or any attachment) contains advice concerning any federal tax issue, it was not written or intended to be used, and may not be used, for the purpose of avoiding federal tax penalties.
 


WIPFLI LLP
Business experts.  Right from the start.
--------------------------------------------------------




SPONSORED LINKS
Computer part Programming languages Microsoft axapta
Support exchange


YAHOO! GROUPS LINKS




Reply via email to