Machine : windows 7
Started : RQM command line adapter.
When initiated test from RQM , I recieve Exit code 1 on the windows machine on which adapter was on.
log file in RQM says:
System error 5 has occurred.
Access is denied.
Bad file descriptor
while running the installation manager thru commandline everything worked fine, Inintiated adapter using the same credentials still its not working.
Any help is highly appreciated.
This error (Access is denied. Bad file descriptor) could be caused by the CLA JAR files being read-only.
Also, the CLA creates temporary files in the directory defined in the java.io.tmpdir system property (on UNIX systems the default value of this property is typically /tmp or /var/tmp; on Windows systems it is typically defined in the %Temp% system variable (e.g. C:\WINNT\TEMP or C:\Users\<username>\AppData\Local\Temp)), which could be full or not sufficient permissions.
Related
The SQL Server 2017 running on a Ubuntu container started to present errors with permissions after the log file went full. Running
create database example
presents
CREATE FILE encountered operating system error 2(The system cannot find the file specified.) while attempting to open or create the physical file '/mssql-translog/translog/example_log.ldf'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
Does anyone knows how to solve this?
I tried to change permissions directly on the container but it says the file system is read only.
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?
I am getting below error when i try to create database with below error -
Directory look up failed with operating system error 3 ( System cannot find the file specifed). Create Database failed.
I am trying to create the database in D: Drive which is a virtual directory created using SUBST command. I tried giving full sql service account permissions to this directory but still failing with error.
Any help would be highly appreciated.
Finally was able to get rid of this error by using physical D: Drive instead of virtual drive.
I am trying to run the Sql Advantage editor but getting below mentioned error.
Internal failure while initializing the SQL Advantage.
Please check that Open Client is configured correctly.
Please check the SET command output in the attached screenshot.Also, I can see two folders in my system for OCS-12_5 and OCS-15_0. This may be causing this problem. I also tried to run a bat file with these commands but getting same error:
Bat file commands:
set SYBASE= C:\Sybase\OCS-12_5
set SYBASE_OCS=OCS-12_5
C:\Sybase\OCS-12_5\sqladv-12_5\sqladv.exe
Please suggest.
SQL Advantage is no longer supported with ASE 15.x
But you can probably still run it if you set your environment to 12.5 (it works for me). Put all the environment settings in a .bat file, and then (in the .bat file) kick off sqladv.exe.
I am having a strange problem with my WPF desktop application that it cant find a shared folder on a server on the local network.
This problem occurs on 2 machines that I have encountered to date.
The path is to a shared folder as I say on a local server pointing to a folder which contains Visual FoxPro database files ( dbf files )
Within my program I get the value of the path from my app.config file.
I then use the path to set up an OLDEB connection to read the data in a dbf file ( visual foxpro table )
I have the path stored as an appsetting in the app config in the following format : \SERVERNAME\sharedFolder
Within my code I retrieve the path value into a variable 'path' and use that value as so : #path
I have also installed the Microsoft Visual FoxPro OLE DB Provider driver.
I installed my program on several windows 7 machines. All of which are part of a workgroup and not a domain. 2 machines out of 5 produce the following exception message " Invalid path or file name. "
UAC settings are the same on all machines also.
On the machines that the error occurs, I can access the shared folder by entering the path ' \SERVERNAME\sharedFolder' in the address bar .. so, the folder is definitely accessible.
I am not sure what else to check if all machines ( as far as I can see ) are set up the same.
Any help would be appreciated.
many thanks in advance
Something to test on a client where it doesn't work is replace the SERVERNAME with the IP address. It could be a DNS resolution issue. (ran into my share of those.)
If it still cannot access that server then I would assume the issue is security. check the users security permissions. If you can get them to log into your dev pc and try running the code so you can see the issue. If not make a test app that just accesses that location and variants such as just \SERVERNAME etc and see what it does. Test read and then write separately.
Obviously check manually that the server can be read from / written to from that PC.