Re: Security Connection Problem
From: Carsten Horlacher (ch_at_seelhof.de)
Date: 02/23/04
- Next message: ginny: "Which SSL Certificate"
- Previous message: Hari: "Re: I/O error (bad page ID) detected during read at offset 0x000000f2ea4000 in file 'F:\TEMPDB\tempdb.mdf'.."
- In reply to: John Jakus: "Re: Security Connection Problem"
- Next in thread: John Jakus: "Re: Security Connection Problem"
- Reply: John Jakus: "Re: Security Connection Problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 23 Feb 2004 14:28:45 +0100
Hi again,
if I understand you right you are setting up a new installation. If so
start Axapta in 2-Tier mode (without AOS) to setup the database. After
the Installation of Axapta it will create the tables within the
database. You have to enter your license codes and do some other stuff.
So this cannot be done in 3-Tier mode. After you make these inital setup
steps you can setup your AOS configuration and access Axapta in 3-Tier
mode.
So you next steps are:
Setup a 2-Tier configuration
Start Axapta and Login as Admin
Follow the steps of the installation checklist
(Compile, Enter license codes, set configuration keys, create users,
initialize help system, ...)
If these steps are passed, you may start the AOS and then connect 3-Tier
thin/fat to your Axapta installation.
If you have further questions, just let me know!
Regards,
Carsten
"John Jakus" <John.Jakus.DieSpammerDie@Valence.com> schrieb im
Newsbeitrag news:ezTJJDe%23DHA.2316@TK2MSFTNGP11.phx.gbl...
> Carsten,
>
> Thank you for the prompt reply. I did not setup the Axapta system. It
> is all new to me. I setup the two Win2K server and the SQL. I am just
> now learning the Axapta system.
>
> I was slowly going through things this evening and found several
> things that need resolving. First the consultent tried installing the
> object server on a dedicated server. With the dedicated server, he was
> getting the same error. After troubshooting with no sucess then tried
> to install directly on the SQL server itself. The same problem was
> encountered.
>
> I have tried different ways to connect to SQL so I don't think the
> problem lies there. Today I examining the system and looking at the
> Navision Axapta Server Manager I saw the following:
>
> The Server Manager is Running
>
> The Object Servers - Server name - Axapta is stopped.
>
> If I try and start it, it just starts for a few moments then stops
> again. Looking at settings, I see that it is using the original
> configuration settings. I seem to remember the consutant having a
> similar problem when it was on the dedicated server. I don't know if
> it was resolved on that server.
>
> I found the following in the Event View Application log after trying
> to start the service:
>
> Object Server Axapta: Login SQL execution error. Server cannot perform
> setup and upgrade tasks. Please perform all setup and upgrade tasks
> using 2-tier configuration.
>
> Looking in the Navision Axapta Configuration Utility, I see that there
> are two configurations listed under the Active Configuration. This
> leads me to believe the consultant was trying differnt methods to get
> this working. It was left on the 2TIER Active Configuration. I don't
> know if this is necessary but the Navision Axapta Server Manager did
> not have a 2TIER Configuration. I tried exporting the settings from
> the Configuration utility for 2TIER then creating a new Object Servers
> configuration in the Server Manger. Then imported the settings. The
> service still will not start.
>
> After trying this, I recived the following in the Event Log
> Application log:
>
> Object Server 2TIER: Failed to create file old\axapd.aoi. Error code
> was 3
>
> and
>
> Object Server 2TIER: Login SQL execution error. Server cannot perform
> setup and upgrade tasks. Please perform all setup and upgrade tasks
> using 2-tier configuration.
>
> I also noticed througout the log this error:
>
> Server Manager: Fatal socket error 10004 occured while receiving
> service requests from clients.
>
> Hope this info is useful. I am new to this. I appreciate any direction
> you can assist with.
>
> Thank You,
>
> John Jakus
>
>
>
> Carsten Horlacher wrote:
>> The message you mentioned is only for inormation and it is not a real
>> error message. How does your axapta configuration file exactly looks
>> like? What database protocol are you running. Are you able to start
>> the axapta client onto the database server? You are running Axapta in
>> 2-Tier mode?
>>
>> Regards,
>> Carsten
>>
>> "John Jakus" <John.Jakus.DieSpammerDie@Valence.com> schrieb im
>> Newsbeitrag news:uY06wsK%23DHA.452@TK2MSFTNGP11.phx.gbl...
>>
>>>I have just setup a new SQL 2000 server (SP3a). We put it on a
>>>Windows 2000 Server with SP4. The server is not part of a domain nor
>>>does a domain exist on the network. The server is setup for Mixed
>>>authentication mode. I can setup connection with DSNs and they work
>>>fine. I am try to get Axapta to communicate and it always gets the
>>>following error:
>>>
>>>"The program is unable to load the execute the class
>>>'SqlDatabaseInit', which is essential in order to identify the
>>>database vendor, and load the appropriate SQL system variables.
>>>
>>>This can be caused by insufficient access rights to the SQL Database,
>>>a missing corrupted applictation file, or syntax error(s) within the
>>>class itself"
>>>
>>>I have tried using local machine authentication and SQL
>>>authentication. Using Administrator account and sa account.
>>>
>>>No problems with any of the SQL utilities or DSNs.
>>>
>>>In the event log I am getting the following errors:
>>>
>>>SuperSocket info: (SpnRegister) : Error 1355.
>>>http://support.microsoft.com/default.aspx?scid=kb;en-us;303411&Product=sql2k
>>>
>>>
>>>SuperSocket info: ConnectionListen(Shared-Memory (LPC)) : Error 5.
>>>
>>>My machine is not part of a domain so is there a way to get rid of
>>>these errors?
>>>
>>>Thank You for any information,
>>>
>>>John Jakus
>>
>>
- Next message: ginny: "Which SSL Certificate"
- Previous message: Hari: "Re: I/O error (bad page ID) detected during read at offset 0x000000f2ea4000 in file 'F:\TEMPDB\tempdb.mdf'.."
- In reply to: John Jakus: "Re: Security Connection Problem"
- Next in thread: John Jakus: "Re: Security Connection Problem"
- Reply: John Jakus: "Re: Security Connection Problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
