Could not execute statement.Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory - sybase-ase

Could not execute statement.
Can't open a connection to site 'SYB_BACKUP'. See the error log file in
the ASE boot directory.
Sybase error code=7205
Severity Level=17, State=2, Transaction State=1
Line 1
enter image description here

The (SAP/Sybase) backupserver is a separate OS process running on the same host as the ASE/dataserver process, so there are a few things you can check:
Have you been able to successfully run dump and/or load commands previously against this dataserver, or is this the first time you've attempted a load command? [If the former then this is likely an issue of the backupserver process not running; if the latter then this may be an issue with an incomplete/incorrect installation of the product.]
Is the backupserver process running on the host where the ASE process is running? [For Windows environments this is usually configured as a service.]
Has the dataserver's SYB_BACKUP (logical) server been configured to reference the correct backusperver name? [Run sp_helpserver SYB_BACKUP and make note of the name under network_name; is this the name of the backupserver?]
Make sure the backupserver is defined in the dataserver's interfaces/sql.ini file. [Is the backupserver - displayed under sp_helpserver/network_name - listed in the sql.ini file?]

Huh. Being new I can't add a comment, so I'm putting it here. What command are you executing?

Related

“Error 1067: The process terminated unexpectedly” when trying to start MySQL

I'm using Windows 7 and running XAMPP MySQL SVC service. I'm seeing the following error:
Windows could not start the Mysql service on Local Computer.
Error 1067: The process terminated unexpectedly.
What does this mean, and how can I fix it?
Examine error log (start eventvwr.msc). MySQL typically writes something to the Application log.
In very rare cases it does not write anything (I'm only aware of one particular bug http://bugs.mysql.com/bug.php?id=56821, where services did not work at all). There is also error log file, normally named .err in the data directory that has the same info as written to windows error log.
You need to:
stop the MySQL service:
Open mysql path\data
Remove both ib_logfile0 and ib_logfile1.
Restart the service
I had the same problem. I am using mysql 5.6.11.
To solve this problem I had to change my-default.ini file in mysql-5.6.11-win32 folder
So I just pasted the following lines under line [mysqld]
basedir="D:\mysql-5.6.11-win32\"
datadir="D:\mysql-5.6.11-win32\data\"
port=3306
server-id=1
bind-address=127.0.0.1
Options basedir and datadir need to be modified for mysql location.
I had the same problem but I was confused with #Vladislav's answer and couldn't seem to find the solution from that. Of course, my problem may not be exactly the same as I encountered the problem when trying to upgrade XAMPP, but it also gave the same Error 1067 message.
With further search I found this:
https://serverfault.com/questions/214435/error-1067-the-process-terminated-unexpectedly-when-trying-to-install-mysql-on
The answer from that is straightforward, that is, to completely clean up the folder, which doesn't always happen. As in regards to XAMPP, I guess I backed up the necessary files first (data folder from mysql folder and the htdocs folder). Uninstall XAMPP. Check the xampp folder for any content that remains and delete everything. You may want to reboot afterwards, just in case. Then reinstall XAMPP. Copy the backed-up folders back to their respective places, and hopefully, mySql will work again in XAMPP.
This should solve the issue.
Same problem here. After analysing log reports via eventvwr.msc I found, that logging files were placed in folder which requires admin rights to update, so files cannot be created and install and startup process could not proceed.
So checking eventlog was very usefull.
I get this problem from time to time, and when I do, I have been able to solve it by using a backup of the database folder(s) that give the problem.
When you check your 'Event Viewer > Windows Log > Application', if you see an error:
InnoDB: Attempted to open a previously opened tablespace. Previous tablespace [database]/[table] uses space ID: 59 at filepath: .\[database]\[table].ibd. Cannot open tablespace [different db]/[different table] which uses space ID: 59 at filepath: .\[different db]/[different table].ibd
Then what works for me, is delete the first mentioned [database] folder in your MySQL data directory, and copy the backup of that database folder to where it was previously.
Then start MySQL, and it starts again for me, without this 1067 error.
Don't forget to check
innodb_data_home_dir = <your_directory_location>
innodb_log_group_home_dir = <your_directory_location>
on my.ini files. Wrong set value for these two variable make mysql process terminated and produce error 1067. Also check eventvwr.msc and mysql_error.log for detail error.
I had practically the same problem. in the log file I found this:
110903 9:09:39 InnoDB: 1.1.4 started; log sequence number 1595675
110903 9:09:40 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'user'; try to repair it
Apparently the user table has been corrupted. I replaced it with another copy (user.frm ; user.MYD ; user.MYI in mysql\data\mysql)
and thats works for me.
ps: am using xampp.
Search and destroy (or move cautiously) any my.ini files (windows or program files), which is affecting the mysql service failure. also check port 3306 is used by using either netstat or portqry tool. this should help. Also if there is a file system issue you can run check disk.
I just went throught same issue and I solved it the following way.
1 - found the .err file which logs all mysql issues, in win7, located under programData\MySQL\MySQL Server 5.6\data\
2 - Check the last entries from the file and, in my case, I found the error was coming from a flag (audit-log) that I set to "true" from the workbench interface the day before!
3 - went into the my.ini file, and removed audit-log=ON.
4 - launched mysql service and it worked!!
I've got the same problem, and what worked for me is in THIS OTHER ANSWER.
I didn't replicated it here because it is NOT A CORRECT THING TO DO.
Basically is a re-install being sure to delete everything very well and using 32 bit versions.
I had the same error. I checked the error logs: C:\ProgramData\MySQL\MySQL Server 5.5\data\inf3rno-PC.err. According to them
170208 1:06:25 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete
170208 1:10:44 [Note] Plugin 'FEDERATED' is disabled.
170208 1:10:44 InnoDB: The InnoDB memory heap is disabled
170208 1:10:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
170208 1:10:44 InnoDB: Compressed tables use zlib 1.2.3
170208 1:10:44 InnoDB: Error: unable to create temporary file; errno: 2
170208 1:10:44 [ERROR] Plugin 'InnoDB' init function returned error.
170208 1:10:44 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170208 1:10:44 [ERROR] Unknown/unsupported storage engine: INNODB
170208 1:10:44 [ERROR] Aborting
I think the important part here
170208 1:10:44 InnoDB: Error: unable to create temporary file; errno: 2
I changed the TMP and TEMP env variables from C:\Windows\Temp to %USERPROFILE%\AppData\Local\Temp yesterday, because I was unable to compress a directory and according to many post the solution is that. Now compression works, but mysql and apparently nod32 complains that they cannot create temporary files...
I added tmpdir=c:/server/mytmp to C:\Program Files\MySQL\MySQL Server 5.5\my.ini. And after that started the service again with services.msc. It is okay now.
So this can be a possible cause as well. I strongly suggest to everybody encountering this problem to check the error logs.
I use install file to repair. it works for me
please check the space available on drive where the db is stored. in my case it was stopped the service due to less space on drive.
There are many solutions for the problem. This worked for me
Right click on Service -> Properties -> Log on as system account.

IBM DB2 unable to access database from PHP after reboot

System: Windows 8
I have been working on a project for school using IBM DB2 Express-C, Xampp, and PHP to access the database.
Everything has been working perfectly. Then one day I rebooted my computer.
IBM Database Manager returned the following error at startup:
SQL5005C The operation failed because the database manager failed to access either the database manager configuration file or the database configuration file.
I have tried running db2stop and db2start.
I am still able to access my database via the db2 command line terminal as if nothing is wrong.
However, when I try to access my database from PHP I now get the following error from my PHP file:
58031
[IBM][CLI Driver] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 SQLCODE=-1031
You might want to double check the db2diag.log to find the reason for SQL5005C. In the better case there was a temporary problem accessing the configuration files. However, in the worse case one of the DBM or DB configuration files may have become corrupt. In the case of a corrupt DBM CFG, I usually use db2idrop/db2icrt. A corrupt DB CFG can be "fixed" (as in "reset", you will lose all custom changes) by RESET DB CFG.
The subsequent SQL1031N tells me the database you are trying to access has been uncataloged. This is also odd, especially since you are telling me you are able to access the database from the DB2 command line. You might want to do LIST DB DIRECTORY from your command line to show your database entries, and also LIST NODE DIRECTORY to see which nodes the databases reside on.
The possible reason is that you lost the database files on your hard disk.
Use command to check.
db2diag -g db=database name > log.txt
open log.txt,you will see the message like below. In this case, I lost some db2 config files.
Create missing folder and copy the db2
config files from the backup
Using backup file to restore database.
When you try to interact with DB2 from a programming language (PHP, python or others) you use a library (example ibm_db for python) that interact with a db2 client application to connect/query your DB.
If you have more than one IBM Data Server client packages installed on your workstation you might not use the right one to access your DB.
So you have to verify which client your PHP api has using to do this job. To do this:
identify your ../clidriver/bin folder that contains your db2 client utilities (in my case it was in my python installation folder/site-packages/ibm_db-2.0.8-py3.6.egg/clidriver/bin
run command db2cli validate that will show you the client you are using
If you have more than one entry in List of all IBM Data Server client packages on the current workstation: and you are not using one of the IBMDBCL_ client, you must switch the client by double clicking on db2swtch.exe (run as administrator) and following the visual instructions to switch to the IBMDBCL_ item
if it doesn't work, uninstall and reinstall your library (in my case pip uninstall ibm_db and easy_install ibm_db)
You can find more information about the management of more db2 client on the same machine here

Symfony: InvalidArgumentException while parsing web.xml

Recently I moved a Symfony-system to another Server and got an error ever since.
The technical details are:
An apache 2.4 server on a windows server 2012
A fileserver which can be accessed by apache over the local network
When I moved the Symfony-page I deleted the cache.
What happens now is, that I get these error-messages:
InvalidArgumentException: Unable to parse file "\\FILESERVER\PAGEPATH\vendor\symfony\symfony\src\Symfony\Bundle\FrameworkBundle\DependencyInjection/../Resources/config\web.xml".
and
InvalidArgumentException: [WARNING 1549] failed to load external entity "file://///FILESERVER/PAGEPATH/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/schema/dic/services/services-1.0.xsd" (in n/a - line 0, column 0)
[WARNING 3084] Element '{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at location 'file://///FILESERVER/PAGEPATH/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/schema/dic/services/services-1.0.xsd'. Skipping the import. (in in_memory_buffer - line 8, column 0)
[ERROR 1845] Element '{http://symfony.com/schema/dic/services}container': No matching global declaration available for the validation root. (in //FILESERVER/PAGEPATH/web/ - line 5, column 0)
What seems to be the problem, that in the first error, there is a mixture of slashes and backslashes in the path but I have no idea how to fix this issue.
This issue is due to using UNC path (\\something). I had the same problem in Windows network enviroment with IIS and Symfony on another server. Unfortunatelly, I wasn't able to find solution. I ended up with having source code on the same machine and using local path.
EDIT: I found one more possible solution - symbolic link.
mklink /d C:\myroot \\FILESERVER\PAGEPATH
Now you can see under C:\myroot content of shared folder. I don't know if Apache will be happy with it but IIS doesn't have problem. And one more thing, be prepared for some performance issues due to network transfer.
I am not sure whether this is related to your problem, but I once experienced problems parsing XML files when the schema definition file could not be loaded at parse time. The parser tried to load the XML schema file via network and in case the network connection failed, parsing the XML file failed as well.
If you are in production, for performance reasons you might not want a schema validation at all, so check whether the used parser offers a way to turn the automatic schema validation off. If however the error occurs in your development workflow, make sure that the schema URLs can actually be resolved from the webserver that parses the XML file.
If the UNC path is the problem, maybe it works if you map the network share to a local drive and use the paths on the local drive to access the application.
Map \\FILESERVER\PAGEPATH to a local drive, let's say W: (W from web) then configure Apache's web root to W:\web instead of \\FILESERVER\PAGEPATH\web. I guess all the other path references are relative and nothing else needs to be changed.
(just a thought)
Update:
As a regular user, you can map a network share as a local drive and have it automatically re-connect on each logon by using the following command line:
C:\> net use W: \\FILESERVER\PAGEPATH /persistent:yes
Apache doesn't run as a regular user (I don't have a Windows system at hand but I think it runs as SYSTEM USER). I cannot tell if the special users "logs on" when Windows starts up.
However, I think it is possible to run the command above (stored in a .cmd file) using the Task Scheduler (on Windows 7 or newer), every time Windows starts.

PostgreSQL first time install and attempt to connect

I just installed postgresql-9.1.4-1-windows-x64 on a Windows 7 64 bit machine. I'm having trouble starting the service and connecting to a database.
After a successful installation I've tried the following based on similar postings.
1) Looked for "Start Server" under Start > All Programs > PostreSQL 9.1 and could not find it.
2) Tried starting the server from the command line
pg_ctl.exe -D "C:\Program Files\PostgreSQL\9.1\bin\data"
This gave me the error:
could not create lock file 'postmaster.pid': Permission denied
I have administrative rights, and there is not postmaster.pid file either in the bin or data directories.
3) Next I tried starting the Service from Admistrative Tools by right clicking on the postgresql-9.1.4-1-windows-x64 Service and selecting Start. I received the message:
The postgresql-9.1.4-1-windows-x64 Service on local computer started
and stopped. Some services stop automatically if they are not in use
by other services or programs.
The Event Viewer showed the error as Timed out waiting for server startup
4) I figured there the data in the data directory was probably and initial database, but just in case I ran "initdb" and got:
If you want to create a new database system either remove or empty the
directory c:\program files\postgreSql/9.1/data or run initdb with an
argument other than c:\program files\postgreSql/9.1/data
4) And just for fun I Started pgAdminIII, right clicked on "PostreSQL 9.1(localhost:5432)", selected Connect, entered password, and got:
could not connect to server: Connection refused (0x0000274D/10061) Is
the server running on host "localhost" (::1) and accepting TCP/IP
connections on port 5432?
Does anybody have a suggestion?
Thanks.
«"could not create lock file 'postmaster.pid': Permission denied"»
Do not look any further, Postgres cannot start if it can't create this temp file. If it is not created, you evidently cannot find it if you look for it on the disk. Your DATA directory has been created so no need to re run initdb again and if you try to use pgadmin it complains that it cannot connect to Pg -- which is not running.
I am not familiar with windows but found out where postmaster.pid is to be created you will probably find out why Postgres cannot create this file.
Hope it helps.

Connection timeout error when launching my program from a shortcut

I'm seeing connection timeout errors when I launch my program from a shortcut.
The error appears when I start the windows application:
error found !! timeout expired. the timeout period elapsed prior to
completion of the operation or the server is not responding
but if I copy folder from c:/program file/myapplication and paste it on D:/ drive and start the application it works fine, but not from start menu and desktop shortcut.
It sounds like your program is getting database connection settings from a file which is in the same folder as the program, and your code is just assuming it will find this file in the current directory. When it is unable to read the settings, it tries to connect using invalid connection settings.
The quickest fix is to right-click the shortcut, select Properties, and change the Working Folder to the program folder.
The better (longer to implement) solution is to either:
Have your program check the folder your program is in and specify the full path when opening your configuration file
Store settings in the registry
Go to run pressing "winkey +r" and write 'msconfig' and check in the Startup applications. If you find myapplication in the list then just disable it.

Resources