on 2014 Oct 13 9:12 AM
Hi,
I have an application that creates a local sqlanywhere-database via process.start (dbinit) /dbstop ...
I installed mysql a few days ago and today I couldn't perform dbstop/dbinit from my code for some reason.
I uninstalled mysql, restarted, tried again, reinstalled sql anywhere, tried again, restarted and tried again... still no luck...
only after connecting to the local database with sybase central things worked again.
Very strange... wanted to hear if someone has ever seen this behaviour before?
What exact error message do you get?
Do you run the DBINIT utilty with specifying a path?
If not, may it be the install/uninstall has removed the SQL Anywhere binaries from the PATH environment variable?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I get a message "File not found". there is no path in process.start ... I have to say, it seems fixed now.. Thanks on the tip of the "PATH environment variable", I was wondering on how process-start could find the path of dbinit without me giving it ... I see them there now, the last one in the list of the "Path environment variable" ... I guess the reïnstall did work afterall...
It's also common practise to add the version-specific SQL Anywhere environment variable to the call of the built-in utilities, such as "%SQLANY12%\\bin32\\dbinit" or "%SQLANY11%\\bin64\\dbinit", primarily to prevent the calling of a utilitiy from an undesired version if you happen to have several SA versions installed in parallel ... cf. that doc page.
User | Count |
---|---|
73 | |
10 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
6 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.