-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm Burtt
Sent: 29 June 2005 23:52
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Ax 2.1 with SQL2000 wnd Windows 2003HiUsing "Change user /install" puts the terminal server into a special mode that ensures registry changes made during the install process happen in a manner compatible with terminal server usage of the software. You still need admin rights to be able to do the install.Using the standard Add/Remove programs option on the control panel automatically executes a "Change user /install" command before the installation begins and reverses it ("Change user /execute") once it completes.RegardsMalcolm
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of James Flavell
Sent: 29 June 2005 14:24
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Ax 2.1 with SQL2000 wnd Windows 2003Hi Malcom,Thanks agian for the input.Reading your post agian I just realised I have never installed anything on a terminal server!!! The change user/install and execute you talk about I am guessing is basically to make sure the install is run with adminstrator rights is it and therfore available to all terminal server users??ThanksJames-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Raul Llorente Peña/OPENSOLUTIONS
Sent: 24 June 2005 19:34
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Ax 2.1 with SQL2000 wnd Windows 2003
I Agree Malcolm.
Raúl Llorente Peña
Análisis, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
"Malcolm Burtt" <[EMAIL PROTECTED]>
Enviado por: Axapta-Knowledge-Village@yahoogroups.com24/06/2005 09:35
Por favor, responda a
Axapta-Knowledge-Village@yahoogroups.com
Para<Axapta-Knowledge-Village@yahoogroups.com> cc AsuntoRE: [Axapta-Knowledge-Village] Ax 2.1 with SQL2000 wnd Windows 2003
Hi James
Our first experience of Axapta was with version 2.1 running on SQL 2000, so I know that works. I don't recall having to do anything special to make it work (probably just as well as we were SQL Server & Axapta newbies at the time).
We have always run inside terminal services and don't get any problems with that either. You will need to install Axapta through the Add/Remove programs function in Windows (or execute the command "Change user /install" before installing and then "Change user /execute" afterwards) or it won't load correctly.
I would install 2.1 as described above from the installation CD (including applying any services packs using the same approach) then replace the Appl directory with your existing one.
Hope that helps.
Regards
Malcolm Burtt
Global IT Group
"Business Solutions designed for YOUR business processes"
Global IT Group is the trading name of Touchstone Global Business Solutions Ltd. and is part of the Touchstone Group PLC.-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of James Flavell
Sent: 24 June 2005 00:42
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Ax 2.1 with SQL2000 wnd Windows 2003
Hi I hope some out there are able to help with a rather old setup...
I have a customer who is running Ax2.1 and they are very happy with it, therefore they do not want to have to go through all the trouble of upgrading etc but they want to run on SQL2000 (due to IT audit security concerns etc).
Does anyone know if it is possible to run Ax2.1 with SQL2000? I know it will not work straight out of the box as I recall for Ax2.5 there was some configuration on SQL you had to do (something about Axapta and SQL reserved words clashing so you had to turn off some features in SQL...or something like that...)
Anyone have an actual site/experience with this configuration?
Also they want to run on Windows 2003 via terminal services, to move the application to such a machine what is the best approach?
1) install a standard ax2.1 and then delete the folders and replace with the actual application?
OR
2) just copy the files to new server (I think this has possible system files not registered problems right)
Is there any know issues with Windows 2003 termainl services and axapta?
Hoping some one can help
Thanks
James
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
---- LSpots keywords ?>---- HM ADS ?>
Sharing the knowledge on Axapta.
---- LSpots keywords ?>---- HM ADS ?>
Sharing the knowledge on Axapta.
YAHOO! GROUPS LINKS
- Visit your group "Axapta-Knowledge-Village" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Title: Message
Hi
Malcom, Andrea, David and everyone else in the group
This
question is a mix of std Axapta understanding and help for a Ax 2.1 SQl7 to
SQL2000 upgrade ....
I have
finally managed to do an upgrade of my customers SQL7 AX DB to SQL2000
using DTS. Everything looks okay on the SQL side but when I try to
launch Axapta 2.1 with the SQL2000 I get the error message:
Index
'I_65531OSACCOUNTNAME' on table 'USERINFO' (specified in the FROM clause) does
not exist
A few
things I am not sure of:
1) Is
this index a temporary index or is this a permanent index (just wondering why it
has a number on the front)? The problem is I cannot see indexes for this
table in Axapta as it is a system table....
2)Is
there any way to view indexes in SQL manager? As I say everything looks okay in
SQL but from what I know there is no way to see indexes so not sure whether they
exist in SQL and have not been copied in the DTS....
3) Any
reason I might get this message and anyway to try to fix it?
I look
forward to cracking this and moving my customer into the 21st century (aka
SQL2000 ...although only partially since they still want to use Ax2.1 ;)
)
Thanks
James
- [Axapta-Knowledge-Village] Axapta and indexes James Flavell
- RE: [Axapta-Knowledge-Village] Axapta and indexes Malcolm Burtt
- RE: [Axapta-Knowledge-Village] Axapta and indexes James Flavell
- RE: [Axapta-Knowledge-Village] Axapta and indexes Malcolm Burtt
- RE: [Axapta-Knowledge-Village] Axapta and indexes James Flavell