four AOS licences - the info in the application log indicates that we have
no more licences available:
Object Server AxSunLive3: Concurrent number of AOS' for this application
exceeds the licensed number.
Regards,
Matt Benic
Axapta Developer
UTi Sun Couriers Division
-----Original Message-----
From: Bjarne R Mikkelsen � A-TEX A/S [mailto:[EMAIL PROTECTED]
Sent: 29 July 2004 10:18 AM
To: [EMAIL PROTECTED]
Subject: SV: [development-axapta] More AOS woes
Hi
Is there any help from the event log? This useually describes the problem.
Best Regards
Bjarne
-----Oprindelig meddelelse-----
Fra: HEW (Helmut Wimmer) [mailto:[EMAIL PROTECTED]
Sendt: 29. juli 2004 09:09
Til: [EMAIL PROTECTED]
Emne: AW: [development-axapta] More AOS woes
Hi Matt
The problem you are describing sounds familiar to me, but we always
managed to get the AOS starting by stopping all AOS and deleting the
axdat.udb file.
Best regards
Helmut
-----Urspr�ngliche Nachricht-----
Von: Matt Benic [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 29. Juli 2004 09:47
An: Axapta Dev
Betreff: [development-axapta] More AOS woes
Hi All,
We are really having a hard time with these damn AOSs. I would really
appreciate any info on intricacies and caveats that could cause what we're
experiencing:
We officially have four AOS instance licences. We have AOS instance
managers (i.e. the Axapta Server Manager) installed on two machines (say AX1
and AX2). We have three Axapta databases, one for development, one for test
and QA and one for live use. We have corresponding applications (meaning the
aod and aoi files) for each database, these are available through a share on
AX1. Each of these databases are instances in the same SQL DBMS on a
separate server (call it DB1).
Ignoring our test and dev environments and focusing on our live
environment, our ideal is to have three clustered AOS instances running on
AX1, using the Live application and database, as well as a fourth AOS
running on AX2, dedicated to performing batch processing (also using the
Live application and database).
Now we have inconsistently been able to achieve this ideal, but since we
had to shut down and restart our batch AOS on AX2, we have not been able to
restart it. We have tried all sorts of configurations, but in the end all we
could get working was to stop one of the AOS's in the cluster, and start our
batch system there instead. We have tried shutting down both server managers
and deleting the .udb file in the application folder, but not even this
allowed us to start all of our AOS's.
There are no other AOS's on the network using this database and
application, not even any two-tier clients. I am really at a loss.. is there
something I am not understanding about the AOS idea and licensing? Can
anyone offer ANY suggestions or point me in the direction of documentation
that may help?
Regards,
Matt Benic
Axapta Developer
UTi Sun Couriers Division
Yahoo! Groups Links
Yahoo! Groups Links
Yahoo! Groups Sponsor
ADVERTISEMENT
----------------------------------------------------------------------------
--
Yahoo! Groups Links
a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
b.. To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
| Yahoo! Groups Sponsor | |
|
|
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.
