Results 1 to 4 of 4
  1. #1
    Join Date
    May 2007
    Posts
    6

    Unanswered: Unable to install ASE 12.5.2 on XP-Urgent

    I’m trying to install Sybase’s ASE 12.5.2 on windows XP. So what I did was:

    - create a ‘sybase’ user account through admin tools-> computer management with administrator rights
    - logged in the ‘sybase’ account ran the setup.exe and go through the prompts in the installation GUI.
    - When the installer tries to complete the configuration process it and tries to reboot the server it is unable to log in. The log is as below.

    Task succeeded: create the master device.
    Running task: update Sybase Server entry in registry.
    Task succeeded: update Sybase Server entry in registry.
    Running task: start the Sybase Server.
    Calling the shell with 'C:\sybase\ASE-12_5\bin\sqlsrvr.exe
    -dC:\sybase\data\master.dat -s'serverName'
    -eC:\sybase\ASE-12_5\install\'serverName'.log -iC:\sybase\ini
    -MC:\sybase\ASE-12_5 '.

    waiting for server 'serverName' to boot...

    WARNING: Cannot determine the status of server 'serverName':
    process is running but unable to log in.
    Task failed: start the Sybase Server. Terminating configuration.
    Configuration failed.
    Exiting.

    -------

    I've tried uninstalling Sybase, deleting the installation folder, clear the registry , reinstalling.

    But it still gives the same error.
    Is there something else I must be looking at?

    I'd appreciate any help as I need to get things going at the earliest

    Thanks in advance,

    M

  2. #2
    Join Date
    May 2005
    Location
    South Africa
    Posts
    1,365
    Provided Answers: 1

  3. #3
    Join Date
    May 2007
    Posts
    6
    Hi pdreyer,

    Thanks of replying. It turned out that increasing the machines swap size to 2 times the available physical memory solved the problem.

    cheers,

    M

  4. #4
    Join Date
    Sep 2003
    Location
    Switzerland
    Posts
    443
    Quote Originally Posted by mxt
    Hi pdreyer,

    Thanks of replying. It turned out that increasing the machines swap size to 2 times the available physical memory solved the problem.

    cheers,

    M
    The first message you posted and the solution you gave doesnt make any sense... Anyways.. good that you got it running

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •