It looks like the Environmental Variable Path exceeded its limit. You will have to do a careful clean. Go to Control Panel - System - Advanced System Settings - Environment Variables Find the Variable with PATH or Path and Edit the text in it. Before editing it, Copy the text from the Variable and Save it somewhere safe, you will need to replace it again.
Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site. Sybase ase Windows 8 downloads - Free Download Windows 8 sybase ase - Windows 8 Downloads - Free Windows8 Download.
The paths in the PATH variable are separated by semicolon (;) for different applications. I just done the second time installation after I remove some of the PATH and restart, it really works better as it ask more this time!! However it said problem during the installation of SCC and when I try to start the SCC service, it just can't! Console said: 'The Sybase Control Center failed to start.
Please check the error log in C: Sybase SCC-32 log for detail and consult Sybase Customer Service & Support at.' And please see attached log. BUT it don't install the Sybase DB as the Windows service!
On the other PC which has this working well will install the Sybase DB as the service. This is the message on the last installation screen: 'The product configuration failed. Please check the product configuration log files in 'C: Sybase ASE-150 init l ogs' and consult Sybase Customer Service & Support at. If you have not done so, please go to to obtain the Sybase software licenses.' And this is the message of the log: 'This directory contains logs of sybinit configuration sessions. The logs are numbered logmmdd.nnn where mm - is the month, dd - is the day of the month, nn - and n is a number that is incremented every time sybinit is run on the same day and month starting with 001.
For example, if sybinit is run twice on January 15 the following files would exist in the init/logs directory: log0115.001 log0115.002 ' I don't think this one making sense. The log says SCC installed correctly. There's not enough information to say what's going on here. I agree a successful Windows install of ASE should create three or four services depending on your version.
Have you had a look at the Release Bulletin for Windows to ensure you have met all prerequisites? I think you need to log a case with Sybase Support for this as either we have no logs at all (I still don't have the log for your most recent ASE install), or the logs say everything installed successfully. Nope, you sent the SCC install log, and what looks like a Windows log, but not the ASE install log from your second attempt, just from your first. 'Working fine on another Windows 7 PC' isn't really useful here - the PATHs and other environment variables will be different; patches could be different; you might have installed in it a directory whose path contains a space on one machine but not on the other. Unless your two machines were freshly imaged from the same image and use the same hardware you can't really compare them. That said I don't understand why this is failing for you.
There's nothing fancy that has to be done to make it work under Windows 7, you don't need any specific versions of patches or libraries. From the ASE-Suite.log: Additional Notes: ERROR - Adaptive Server Enterprise: FAILED. See log file C: Sybase log ase.log for detail. Select all and Additional Notes: ERROR - The product configuration failed. Please check the product configuration log files in 'C: Sybase ASE-150 init logs' and consult Sybase Customer Service & Support at Select all So I need that C: Sybase log ase.log and whichever file has the most recent timestamp in C: Sybase ASE-150 init lo gs. How many characters is your PATH currently?
Have you rebooted between reducing the length of your PATH and reinstalling ASE? I ask because that log has this in it: Status: ERROR Additional Notes: ERROR - WindowsEnvironmentVariable Action.upd ateEnv: can not set env PATH because value exceed max length. Remember changes to environment variables are not visible to processes until Windows is restarted. I am guessing this is at the root of all your issues - the ASE installer cannot properly update the current value it can see of PATH, and as a result other environmental issues are failing.
I agree 99 chars should be plenty short enough, but unless there was a reboot between editing PATH and reinstalling ASE, the installer is still using the old (too long) version. If you did restart Windows, then I'm not sure what the issue is, but that ase.log is complaining about the PATH, and until that is fixed, nothing else will work reliably or at all. Joe, AHAHHAH now, it is really working as you point out, but the SCC only STARTABLE if I restart the PC. The message after the installation is: 'The Sybase Control Center failed to start. Please check the error log in C: Sybase SCC-32 log for detail and consult Sybase Customer Service & Support at. The product configuration failed. Please check the product configuration log files in 'C: Sybase ASE-150 init l ogs' and consult Sybase Customer Service & Support at.
If you have not done so, please go to to obtain the Sybase software licenses. ' see the attached log files. Everything else depends on what the ASE installer does in terms of setting environment variables. Including PATH. If that isn't correct then little else will work. 1) So my guess is SCC didn't work the first time because you hadn't rebooted, so PATH had not been updated. Then you rebooted, and SCC was able to access to new and correct PATH.
2) You never directly start or stop the XP Server. ASE will start it for you as required (if you call any extended stored procedure or xpcmdshell), and will shut it down when ASE shuts down. This is correct and expected. '1) So my guess is SCC didn't work the first time because you hadn't rebooted, so PATH had not been updated.
Then you rebooted, and SCC was able to access to new and correct PATH.' Then why the installer don't prompt for reboot? It is version 15.7 already, still have this kind of minor problem. '2) You never directly start or stop the XP Server. ASE will start it for you as required (if you call any extended stored procedure or xpcmdshell), and will shut it down when ASE shuts down. This is correct and expected.
' but if I start it manually! It prompts an error!
Is it normal too? Scc service don't need to start too? 'When ASE starts the XP server it must add some extra stuff to make it work - it's not really the same kind of server in that you can't ever connect to it even when it's running, it's just a bunch of dedicated code for talking to the OS.
' hard to see why a service can operate like this! Then it can't simply do not register as a windows service, right? What I am worrying about is, if that XP can't start manual, when operating the Sybase 15.7, it fails. But in what situation this service will run? I want to try it! It should be at least, start manually.
'Start the ASE and BS, you'll need that for any backups or restores.