foxmail老是显示错误怎么回事_百度知道
foxmail老是显示错误怎么回事
：-ERR 您没有权限使用POP3功能此问题主要来自于126/163邮件服务器的限制. 主要受限制的是新申请的用户.老客户不受此问题的影响. 如果您是163的用户，可以免费将邮箱升级到3G邮箱，升级后即可支持使用Foxm#3：&-ERR LOGON FAILURE: UNKNOWN USER NAME OR BAD PASSWORD.&您输入了错误的用户名或者密码. 请重新检查您帐户的设置. 注意: 一些邮件服务器区别大小写, 您要留意您输入的大小字母的差别#8：&-ERR HOTMAIL HTTP/1.1 402 ACCESS TO HOTMAIL VIA OUTLOOK AND OUTLOOK EXPRESS NOW REQUIRES A SUBSCRIPTION. PLEASE SIGN UP AT &的邮件服务已经不再对用户免费开放了. 除了个别活跃老用户仍然可以继续使用外,其他用户,包括新用户(2004年以后注册的)必须到#10：&-ERR [SYS/PERM] YOUR ACCOUNT IS NOT ENABLED FOR POP ACCESS. PLEASE VISIT YOUR GMAIL SETTINGS PAGE AND ENABLE YOUR ACCOUNT FOR POP ACCESS.&您没有在GMAIL中开放POP3功能. 请按官方设置,在webmail的option里选择支持pop即可收信 #78：用FOXMAIL,能收邮件不能发能收邮件,不能发.提示:smtp server reply:535 error :authentication failed 出现此问题, 主要是您的帐户没有通过SMTP的服务器验证. 要解决此问题: 1)确定您的帐户名,密码没有输入错误. 2)请在帐户属性-&邮件服务器-&SMTP服务器需要身份验证 选项上打钩.#7018：-ERR [SYS/PERM] YOUR ACCOUNT IS NOT ENABLED FOR POP ACCESS. PLEASE VISIT YOUR GMAIL SETTINGS PAGE AND ENABLE YOUR ACCOUNT FOR POP ACCESS.您的GMAIL还没有开放POP3功能, 请在GMAIL的网站上设置.#7036：SMTP server reply : 550 Error con tent rejected.此问题主要是因为: 发送的邮件内容疑似垃圾邮件,系统拒绝接收, 因此您不能再发送邮件了. 许多邮件服务器为了防止垃圾邮件,都加入了自己的反垃圾机制.如果您被服务器认为是发送了垃圾邮件, 您应该向#7037：只能收邮件不能发邮件每次点击发送就会弹出一个对话框： File open Error： Foxmail/OUT BOX OUT.BOX损坏. 把OUT文件备份后删除,重新启动FOXMAIL即可.#7040：不能发送邮件发送邮件时出现错误：SMTP server reply:500 error :bad syntax. 用的126的邮箱 您邮件的发件人的地址不合法, 请您检查您的邮件地址的格式, 常见如: 地址后面多了'符号,导致邮件服务器认为地址不合法.#7041：系统错误
错误号：6757
错误信息：Error while storing the request's serial in cert-object 您在FOXMAIL中选择了&数字签名&. 请注意: 请误把&数字签名&当做邮件签名. 要解决此问题, 请在选项中去掉&数字签名&这项, 就可以正常发送了.
其他类似问题
为您推荐：
foxmail的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁OceanStor 0 V3&0 V3&6800 V3 Storage System V300R003 HyperMetro Feature Guide 04 - Enterprise Service Support
(HedEx Lite required)
Download and install the latest HedEx Lite version. Then, restart the browser.
Alternatively, upgrade the current HedEx Lite to the latest version.Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide, Release 4.5(1) - Error and Event Log Messages [Cisco NAC Appliance (Clean Access)] - Cisco
Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide, Release 4.5(1)
Book Contents
Book Contents
Download Options
Book Title
Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide, Release 4.5(1)
Chapter Title
Error and Event Log Messages
View with Adobe Reader on a variety of devices
Chapter: Error and Event Log Messages
Chapter Contents
Error and Event Log Messages
Clean Access Server is not properly configured, please report to your administrator.
A login page must be added and present in the system in order for both web login and Clean Access Agent/Cisco NAC Web Agent users to authenticate. If a default login page is not present, Agent users will see this error dialog when attempting login. See also .
Clean Access Server could not establish a secure connection to the Clean Access Manager at
&IP_address&
This error message to clients attempting login () commonly indicates one of the following issues:
oThe time difference between the CAM and CAS is greater than 5 minutes.
oInvalid IP address
oInvalid domain name
oCAM is unreachable
See also .
Figure&A-1 &CAS Cannot Establish Secure Connection to CAM&
The request has timed out. [12002]
This error () indicates a communication issue between the Agent and the CAS. The Agent pops up initially indicating that the Agent is able to reach the CAS and vice versa. However, at some point the communication is lost resulting in the error message. This error can reflect a timing issue after the VLAN has been changed for the user machine in OOB deployments. Increasing the VLAN Change Delay (under OOB Management & Profiles & SNMP Receiver & Advanced Settings) from the 2 second default to 3 or 4 seconds may resolve the issue.
Figure&A-2 &Request Has Timed Out 912002]& (Windows Vista Clean Access Agent Example)
Failed to add user to the list
During CAS fallback recovery (where the CAS is reconnecting to the CAM), a login dialog appears to users accessing the Cisco NAC Appliance network via the CAS, but they are unable to authenticate and login for approximately 2 minutes. (Until CAS fallback recovery completes, users see a &Failed to add user to the list& error message when attempting to log in.)
For more information on CAS Fallback design and implementation, see the &CAS Fallback Policy& section of the
Figure&A-3 Failed to add user to the list
Error 1316. A network error occurred while attempting to read from the file
This error () appears when the user attempts to upgrade the Clean Access Agent using an MSI installer filename that does not match the InstallShield Wizard syntax.
To address this issue, make sure the.msi file is named &CCAAgent.msi& before installing it, particularly if downloading the file from Cisco Secure Software (where the version may be specified in the download filename). Renaming the file &CCAAgent.msi& ensures that the install package can remove the previous version then install the latest version when upgrading the Clean Access Agent on clients.
Figure&A-4 Clean Access Agent Unable to Upgrade Using MSI
The &Failed to add Clean Access Agent icon to taskbar status area& error () can occur in the following instances:
Figure&A-5 Clean Access Agent Icon Does Not Install to Taskbar
1. The user tries to run the Clean Access Agent from the icon before the installation is complete. This can occur for both Agent users with admin rights on the computer and Agent users without admin rights and with the Agent Stub installed on the client machine. To resolve this issue, close all installation dialog boxes on the client.
If you continue to receive the error:
a. Restart the client machine.
b. Uninstall and reinstall the Clean Access Agent. Refer to
for how to uninstall the Agent.
2. In certain rare occasions, the Clean Access Agent is not added to Windows task bar during bootup. As a result, the user is not able to perform SSO and/or the Agent login dialog may not automatically pop up for the user. This issue appears related to interaction between the installer and software loaded on the client machine that is resetting the system tray application during the install.
On Agent install, the Windows Start menu is changed and the Windows OS tries to contact AD (in some cases where the AD credentials are expired). Because the Agent machine is in the Unauthenticated role, the AD cannot be contacted to refresh the Start menu. This operation takes about 60 seconds to timeout, during which the taskbar (Start menu, system tray, and task bar) are locked. The Clean Access Agent then displays the &Failed to add Clean Access Agent icon to taskbar status area& error as result.
To resolve this issue, you can:
oAllow AD traffic through the CAS in the Unauthenticated role.
oStart the Agent manually (from the desktop shortcut) after installation if auto load fails.
describes Clean Access Manager event log messages. You can view the even log in the Clean Access Manager admin console from Monitoring & Event Logs.
Table&A-1 Event Log Messages (Sheet 1 of 4)
&MAC address& added to AP MAC list
The access point is successfully added to the access point list.
Normal configuration log
&MAC address& could not be added to the AP MAC list
Adding access point to a pas the Clean Access Server might not be connected.
Error occurred when trying to automatically add to passthrough list
&MAC address& removed from the MAC list
Access point removed from the list.
Normal configuration log
&MAC address& could not be removed from the AP MAC list
Removing the access point from the pas the Clean Access Server might not be connected.
Error occurred when trying to remove from a passthrough list
&Authentication Server Name& added to authentication server list
Authentication server is added to the list.
Normal configuration log
&Authentication Server Name& is already configured in authentication server list
Authentication server being added is already on the list.
Normal configuration log
Provider name &Authentication Server Name& is already been used by different authentication server
Authentication server updating authentication server failed.
Error on authentication server update
&Authentication Server Name& updated to authentication server list
Authentication server updated successfully.
Normal configuration log
&Authentication Server Name& is not a valid authentication server
Authentication
not a valid authentication server.
Error on authentication server update
&Authentication Server Name& removed from the authentication server list
Authentication server removed successfully.
Normal configuration log
&User name, MAC, IP& - Logout request
IPSec Client user logout request.
Normal configuration log
&User name, MAC, IP& - L
U Clean Access Server is not connected.
Invalid user credentials, &User name, MAC, IP&
Username and password invalid.
Invalid authentication provider, &Provider Name& &User name, MAC, IP&
User authentication server invalid.
&Clean Access Server IP& is inaccessible!
Heartbeat between Clean Access Manager and Clean Access S the Clean Access Server is offline.
C Clean Access Server should be brought up immediately
Dhcp properties are added
DHCP properties are published to DHCP server in Clean Access Server.
Normal configuration log
Dhcp properties are not added
DHCP properties publishing to Clean Access Server failed.
Error while publishing DHCP properties to the Clean Access Server
Cleared the event log
The entire event log has been cleared.
Normal configuration log
Domain authentication server information not available
U authentication server information not available.
Error on user login
Domain authentication server information not set
U authentication server information not completely configured.
Error on user login
&MAC address& added to MAC list
Device MAC address is added to the list.
Normal configuration log
&MAC address& could not be added to the MAC list
Device MAC address is not added to the list.
&MAC address& is already in the MAC list
Device MAC address already added to the list.
Normal configuration log
&MAC address& removed from the MAC list
Device MAC address is removed from the list.
Normal configuration log
Updated policy to &Clean Access Server IP&
Policy is updated successfully.
Normal configuration log
Could not update policy to &Clean Access Server IP&
Policy update to Clean Access Server failed.
Could not update policy to all Clean Access Servers, policies will be published whenever connected
A global policy is not updated to all Clean Access S some of the servers might be disconnected.
Normal configuration log. Not an error, as the policies will be updated when they are connected.
Unable to ping &User IP&, going to logout user &Username&
Ping manager is logging off user, as the user is not online. Automatic user log off feature.
Normal user log
&Role name& role already exists
A role by this name has already been created.
Normal configuration log
&Role Name& role is created successfully
The role has been created successfully.
Normal configuration log
Deleting role &Role Name& failed, Clean Access Server &Clean Access Server IP& is not connected
D Clean Access Server is not connected.
Could not connect to &Clean Access Server IP&
Clean Access Server could not be added to the Clean Access Manager a the Clean Access Server is offline or not reachable by the Clean Access Manager.
&Clean Access Server IP& added to Clean Access Manager
Clean Access Server is added successfully to the Clean Access Manager administration domain.
Normal configuration log
&Clean Access Server IP& updated in Clean Access Manager
Clean Access Server is updated successfully.
Normal configuration log
&Clean Access Server IP& is not configured in Clean Access Manager
Updating Clean Access S Clean Access Server information not found in the Clean Access Manager.
&Subnet/Netmask& is already in the SUBNET list
Subnet has already been added to the subnet list.
Normal configuration log
&Subnet/Netmask& removed from the SUBNET list
Subnet is removed from the list successfully.
Normal configuration log
&IP Number& System Stats
Runtime statistics for the identified Clean Access Server. The information is:
oload factor - Current number of packets in the queue that the server is processing (i.e., the current load being handled by the Clean Access Server).
omax since reboot - The maximum number of packets in the queue at any one time (i.e., the maximum load handled by the Clean Access Server).
omem - The memory usage statistics. This lists the used memory, shared memory, buffered memory, and unused memory.
ocpu - The processor load on the hardware.
Unable to process out-of-band login request from [&MAC address& &IP&address&] &username&. Cause: connected device [&MAC address&] not found.
This error message appears when the CAM does not receive appropriate MAC Notification about the client machine. Three common causes for this error condition are:
oThe SNMP trap syntax from the managed switch is not compatible with the SNMP trap syntax on the CAM. (Ensure the syntax/configuration between the switch and the CAM is consistent.)
oThe client machine is already connected to a switch port on the Authentication VLAN before the CAM is configured to manage the switch, thus the CAM cannot authenticate the OOB user login request because the CAM is not aware of the client machine connected to the switch port. (Try disconnecting the client machine from the switch port and reconnecting.)
oThere are one or more device filters acting upon the client machine MAC address and/or the client machine MAC address appears as an exempt device in the CAM's Certified Devices List.
Was this Document Helpful?
Let Us Help
(Requires a )
Related Support Community DiscussionsDatabase access information
Advanced report design
Database access information
This documentation will help you to solve problems and setup your database.
Check installation
Before beginning the troubleshooting you should check this items:
Install the client database software correctly, and server database if needed
Check your database connection with a standard TCP/IP connection application
provided by the database vendor. Check you can access tables and fields executing
some querys
Install additional software if needed, for example if you plan to access
the database throught ODBC, install the ODBC software (unixODBC in Linux/ODBC32
in Microsoft Windows) and make sure to use ODBC driver compatible with the
version you installed. Again check ODBC connections with the provided ODBC
client tools.
Check you are using the correct or latest drivers, for example for Visual
FoxPro you should download the ODBC driver update from Microsoft web site.
This will ensure the database software is correctly installed.
Database drivers overview
There are some database drivers to connect with Report Manager to databases,
usually a connection can be done using different database drivers, each database
driver can have issues or bugs, if you find a issue using a database driver
you should ask about the issue in a correct place.
Driver Name
Vendor/Autor
Some SQL Servers
Borland newsgroups about dbexpress
DBExpress-OpenODBC
Edward Benson
Borland newsgroups about dbexpress
Borland Database Engine
See bellow
Borland newsgroups about BDE
Zeos Library
Some SQL Servers, see bellow
http://zeoslib.sourceforge.net
Microsoft DAO
OLE DB/ODBC Capable databases
Borland newsgroups about adoexpress or dbgo
Interbase Express
Interbase/Firebird
Borland newsgroups about InterbaseExpress
Jason Wharton
Interbase/Firebird
Text files, xml and binary compatible TClientDataset files
Borland newsgroups about TClientDataset and Report Manager mail list
You can also purchase drivers to third party, usually for a fee, you can find
more DBExpress drivers, more ODBC drivers etc.
DBExpress is a technology introduced by Borland since the release of Delphi
6, as a replacement for the Borland Database Engine SQL Links, see section about
BDE bellow for more information.
DBExpress libraries are small and efficient, they are easy to update when a
version change of the vendor occur.
The main problem is that, Borland, the main developer of DBExpress drivers,
does not frequently update this drivers, because limited resources etc.., this
is a important issue because some database engine change versions often, this
changes introduce sometimes incompatibilities (PostgreSQL, MySQL).
Borland was not released sourcecode of DBExpress drivers (but released the
specification so third party can write them), so you can't update the Borland
provided DBExpress drivers.
Provided DBExpress drivers:
Database Name
Linux vendor Lib
Windows vendor lib
Interbase 6.0-7.1/Firebird 1.0-1.5
libsqlib.so
dbexpint.dll
libsqldb2.so
dbexpdb2.dll
db2cli.dll
libsqlmy.so.1
libmysqlclient.so
dbexpmysql.dll
lubmysql.dll
libsqlmy23.so
lubmysqlclient.so
dbexpmys.dll
libmysql.dll
libsqlora.so
libclntsh.so
dbexpora.dll
libsqlinf.so
libinfclient.so.1.0.0
dbexpinf.dll
isqlb09a.dll
Microsoft SQL Server
dbexpmss.dll
oledb (native)
libdbxoodbc.so
libodbc.so
dbxoodbc.dll
odbc32.dll
Troubleshooting for all drivers
Check the libraries you need are in your system, you can also check dependences.
If you have problems with some datatypes you can try to set BlobSize to a value
like 10000
Unable to load library &libraryname&
This message is raised when the vendor librarys are not installed or are a
different incompatible version, it's reported to work to install the correct
version for the DBExpress driver.
Note that the error message usually refers to the DBExpress driver library,
not the vendor library but the problem is in the vendor library.
For example when using Oracle 9i, you can install the Oracle 8i client library
in the directory where Report Manager is installed, so Oracle 8i client library
will be used, this is usually not recomended by the database vendor, so be aware
of the risk, especially when updating the database (working with report libraries).
Check the dependences with a programming tool, for example in Linux:
ldd libsqlpg.so
It reports a link to libpq.so.2 so you should create a symbolic link if this
library does not exists:
ln -s /usr/lib/libsqlpg.so.2 /usr/lib/libsqlpg.so.3
Borland Database Engine
Borland Database Engine was released by Borland since the first version of
Delphi, and have been updated until Delphi 6.
It's not provided by default on Report Manager, unless you purchase the .
It's a really mature engine, but is big and have some overhead when accessing
to SQL servers. It's very good to access DBase, Foxpro, and Paradox
files because it includes a Local SQL processing engine for
this file based databases, can also access text files and have a automatic and
mature ODBC bridge. It has an interesting and flexible database
connection manager, you can configure and test database connections using Borland
Database engine configuration at the control panel.
The SQL Links are libraries installed with the Borland Database
Engine, this SQL Links will not be updated in a future and was not updated from
Delphi 6 release, I think from 2001, so you can have problems if you access
a database server wich changed the client/server protocol or client libraries
since that date. If you want continuing using BDE and the SQL Link is
out of data you can create a ODBC connection, and install the correct
driver for the newer database version.
The SQL Links provided are:
Interbase (also works for Firebird) supporting only Dialect 1
Microsoft Access
Microsoft SQL Server
Borland replace the BDE SQL Links with DBExpress, because BDE is big in size
(and functionallity), it's not cross-platform, and the update and programming
of SQL Links (drivers for SQL engines) is a difficult thing, and can be done
only by Borland. So for all SQL Servers is recommended the use of DBExpress.
Microsoft DAO
This driver is based on Borland interface to Microsoft Data Access Objects,
it only works in Microsoft Windows, there is a wizard to build connection strings
to connect to any installed OLE DB provider or ODBC datasource. This is a common
system for database connection for Microsoft enabled development environments
like Visual Basic, Visual FoxPro...
is a component set
to access some database engines, it's compiled inside all Report Manager binaries,
so you can use it normally, but if you use Report Manager components and want
to add the support in compilation (Kylix/Builder/Delphi) modify the rpconf.inc
file to enable the Zeos Library compiling and linking.
Usually you set the hostname, database, user name and password, but other parameters
are available like the TCP/IP port and character set.
To configure ZeosLib connections the same files as DBExpress drivers are used
(dbxdrivers and dbxconnections).
This driver is allows reading of TClientDataset files (.cds) in binary or XML
format, also allows reading of text files as a database.
The protocol property allow the selection of the database server. It supports
Mysql,Ppostgresql, Interbase/Firebird, Microsoft SQL Server, Sybase, Oracle
and IBM DB2.
Interbase Express
This driver is based on Interbase Express components provided by Borland in
Delphi/Kylix and C++Builder environments, the main advantage is that no external
shared object libraries are needed.
Interbase Objects
This driver is only available for Windows, it's implemented but not provided
because it's a comercial product. Allow access to Interbase and Firebird.
This driver is allows reading of TClientDataset files (.cds) in binary or XML
format, also allows reading of text files as a database.
Getting to work all databases and database drivers in Suse 9.0
This section will give you the steps to configure and use the databases provided
in Suse 9.0. For each database different drivers will be used.
PostgreSQL
Execute Yast, install PostgreSQL server packages and client packages (this
where not installed by default), the important file missing by default to install
is libpq.so.3, located at a client library package. I went to Software installation
selected search postgre and checked all related packages to be sure.
Related packages: postgresql-libs pgaccess postgresql
First step is to start and setup the server I had some problems here because
I'm new to PostgreSQL, I don't know if the way I do things is ok but it worked,
I don't know why this steps are not done automatically by the setup scripts
in software installation. Of course that forced me understanding how PostgreSQL
works, learn reading documentation and also loosing lot of time.
We will also install the unixODBC related packages and the qt and tk interfaces
for configuration, this is for testing purposes , if you do not plan to use
ODBC you don't need them. This are packages: unixODBC unixODBC-gui-qt unixODBC-gui-tk
The startup script uses the postgres user to launch the PostgreSQL server for
security reasons, so this user have limited privileges but should have all the
privileges for the main &database repository&, we will create a database
directory and give ownership to this user.
Login as root and type:
mkdir /var/pgdata
chown postgres /var/pgdata
Now we must initialize the &database repository&, but we must do
it with postgres user, another problem here, I dont know the postgres default
password, so I changed the password with the Yast configuratoin tool.
Login as postgres and type:
initdb -D/var/pgdata
This initializes the &database repository&.
Before starting the service we should say to the startup script /etc/init.d/postgresql
the location of &database repository&. I did it by executing the Yast
tool: Editor for /etc/sysconfig. Go to the branch Applications-PostgreSQL and
POSTGRES_DATADIR /var/pgdata
POSGRES_OPTIONS -i
The -i option is to tell PostgreSQL to listen TCP/IP incoming connections.
Now we will start the database server but we will need to restart in a few
minutes. Go to Yast and execute the tool: Execution Level editor. Select PostgreSQL
and check levels 3 and 5, select start and check it's started.
Loign as posgresql and type:
createuser yourloginname
You will be asked, let the user create databases and optionally users.
Now you are a postgresql database user, we will create a database:
Login as yourloginname and type:
createdb test
Still not finished, we must say PostgreSQL wich IP connections are able to
connect to the database server, by default all connections are closed.
Login as postgres and type, or edit with your favourite editor:
vim /var/pgdata/pg_hba.conf
Remove the # symbol from the line:
host all all 127.0.0.1 255.255.255.255 trust
Now we need to restart the postgresql service, go to Yast Execution Level Editor
and restart the service.
Login as yourloginname and create some data.
I executed pgaccess from a X-Window console to start a client application to
connect to database test, this application uses also TCP/IP, so it's usefull
to test a connection, other tools like createdb are not usefull to test connection
configuration because does not use TCP/IP.
Now we are sure PostgreSQL is up and running correctly.
PosgreSQL with DBExpress
Go to Report Manager connections configuration window, select PostgreSQL and
click add.
After configuring the hostname as localhost, the database name as test, and
placing login information (the same as your login) It does not work, a error
message is raised: library libsqlpg.so can not be found.
But the library is in the path, this is a problem with the vendor library,
lets see executing:
ldd libsqlpg.so
This commands shows a link to libpq.so.2, but in my system I have a library
libpq.so.3, I cross my fingers and expect libqt.so.3 be compatible with the
expected libpq.so.2.
Login as root and type:
ln -s /usr/lib/libpq.so.3 /usr/lib/libpq.so.2
This creates a symbolic link to the newer library, I think you can have problems
if you use features available only with the newer version. But it works ok.
For consistency we will create another link:
Login as root and type:
ln -s /usr/lib/libpq.so.3 /usr/lib/libpq.so
PosgreSQL with Zeos
Go to Report Manager connections configuration window, select ZeosLib and click
Select protocol PostgreSQL, database as test, hostname as localhost and set
user_name and password, you can left the port to default 0.
It does not work but it says correctly the missing library: unable to find
Login as root and type:
ln -s /usr/lib/libpq.so.3 /usr/lib/libpq.so
Now it works. I created a report library to test functionallity but before
I executed from pgaccess:
CREATE DOMAIN BLOB as bytea
PosgreSQL with DBExpress-OpenODBC
After installing unixODBC to allow odbc connections to the database a script
must be executed.
Login as yourloginname and type:
psql -d test -f /usr/share/psqlodbc/odbc.sql
We need to create a ODBC data source.
I executed ODBCConfig (as root) and created a System DSN, to access databases
from other services you should add a System DSN instead a User DSN, for example
to access from Report Manager web server (that is executed from apache for example).
You must add a driver:
I setup Driver Name as POSGRESQL. Driver as /usr/lib/psqlodbc.so Setup as /usr/lib/unixODBC/libodbcpsqlS.so
Then add a System DSN and assign parameter values to each item, Database, UserName,
Password. Save configuration.
I execute qtodbctest to check the connection without success. I think /etc/unixODBC/odbc.ini
contains a setup configuration incorrect for this PostgreSQL version, again
a configuration nightmare, this was so simple as providing a odbc.ini sample
entry in the psqlodbc pacakage, but there is no documentation, oh yes documentation
about how to build the driver (make clean..) but none about how to install it.
This driver cannot be tested with Report Manager because it fails with basic
ODBC connections tests (qtodbctest). Note that in Suse 8.2 and Suse 7.3 the
ODBC driver for PostgreSQL worked without problems.
Intallation is done using software package installation in Yast, intall mysql
package, then the service is activated using Execution Level Editor also in
Yast (select 3 and 5 execution levels).
Install also the client libraries, in this caso mysql-shared package contains
the libmysqlclient.so.12 libraries, mysql-client will be useful for installation
Login as yourloginname and type:
It will show you the database test.
I installed mysqlcc, a usefull client tool. Note that by default you must not
enter any password when connecting to mysql, that is to access your database
server connecting with mysqlcc set Host Name as localhost, User name as yourloginname
and blank password. It will connect and show you databases, I created a test
table an populated it.
Zeos and MySQL
Open Report Manager dataacess configuration, select ZeosLib and click add,
select a connection name, select the new connection, set Database Protocol to
mysql, Host Name to localhost, Database to test, User_Name to yourloginname
and important, blank password, Suse 9 default installation is with blank passwords
for MySQL.
When you click Test connection, a error is raised: libmysqlclient.so not found.
To solve the problem you must provide a symbolink link to the correct version
of MySQL client library.
Login as root and type:
ln -s /usr/lib/libmysqlclient.so.12 /usr/lib/libmysqlclient.so
Retry your connection with yourloginname user. Now it works ok.
DBExpress and MySQL
Open Report Manager dataacess configuration, select MySQL and click add, select
a connection name, select the new connection, Host Name to localhost, Database
to test, User_Name to yourloginname and important, blank password, Suse 9 default
installation is with blank passwords for MySQL.
If you test the connection a error is raised: libmysqlclient.so not found.
Login as root and type:
ln -s /usr/lib/libmysqlclient.so.12 /usr/lib/libmysqlclient.so
But still the same error is launched, this is because DBExpress find a diferent
version of the driver not supported by the DBExpress driver. You need a previous
version of the client library for example libmysqlclient.so.10 search it at
google for example and install in your system, to be persistent about the libmysqlclient.so
is the latest edit your dbxdrivers file in ~/.borland and set vendor lib to
of mysql driver to libmysqlclient.so.10. Now you are using a different client
library. This is a bit dangerous because you are using a wrong client library,
but should work.
DBExpress OpenODBC and MySQL
Installation of MySQL odbc driver is needed. You must install package MyODBC-unixODBC.
You can read the documentation provided (you can see the files of the package
executing rpm -ql MyODBC-unixODBC)
After the installation you can add to /etc/unixODBC/odbcinst.ini file this
[myodbcdriver]
Description = MySQL ODBC Driver
Driver = /usr/lib/unixODBC/libmyodbc.so
And add to /etc/unixODBC/odbc.ini this section:
Driver=myodbcdriver
Description= Test of DSN for MySQL
SERVER=localhost
USER=yourloginname
Database=test
Now you can test the connection with qtodbctest (remember, blank password and
yourloginname). Full connection must be correct.
Open Report Manager dataacess configuration, select OpenODBC and click add,
select a connection name, select the new connection, and set Database to myodbc
(the DSN name) the User_name to yourloginname and blank password.
In this case the test connection failed (the driver hangs), so a bug report
to OpenODBC driver project should be posted
Intallation is done downloading the sofware from
Login as root and type
rpm -U FirebirdSS-1.5.0.4027-RC7.i686.rpm
Then use Execution Level editor to startup the server and activate at runlevels
To check installation:
We create a directory for databases, giving privileges only to firebird user:
mkdir /var/data
chown firebird /var/data
cd /opt/firebird/bin
./isql -user SYSDBA -password masterkey
CREATE DATABASE '/var/data/test.fdb';
Now test connection:
./isql -user SYSDBA -password masterkey localhost:/var/data/test.fdb
Login as yourloginname:
To create some I used IBAccess (),
after downloading:
tar zxvf ibaccess-1_18.i386.tar.gz
./ibaccess.sh
A symbolink link must be created because this tool uses Interbase Express,
this link is also necessary to work with Interbase Express driver in Report
Login as root and type:
ln -s /usr/lib/libfbclient.so /usr/lib/libgds.so.0
Now you can use ibaccess to create a test table.
Firebird using Interbase Express
You must generate a symbolic link to enable Interbase Express:
Login as root and type:
ln -s /usr/lib/libfbclient.so /usr/lib/libgds.so.0
Now you can create a connection and set the type to IBX. Configure the connection
in the same way as a DBExpress Interbase connection.Set database to localhost:/var/data/test.fdb
and it's working.
Firebird using DBExpress
You must generate a symbolic link to enable Interbase Express:
Login as root and type:
ln -s /usr/lib/libfbclient.so /usr/lib/libgds.so
Now you can create a connection and set parameters for that connection. Set
database to localhost:/var/data/test.fdb and it's working.
Firebird using Zeos
Open Report Manager dataacess configuration, select ZeosLib and click add,
select a connection name, select the new connection, set Database Protocol to
Firebird-1.5, Host Name to localhost, Database to /var/data/test.fdb, User_Name
to SYSDBA and password to masterkey.
When you click Test connection, a error is raised: fbclient.so not found. To
solve the problem you must provide a symbolink link to the correct version of
Firebird client library.
Login as root and type:
ln -s /usr/lib/libfbclient.so /usr/lib/fbclient.so
Retry your connection, now it works ok.
Oracle and DBExpress (by Stefano Tronu -stefano.)
1) Installing latest version of Oracle Client (10g actually) (for
example on /usr/lib/oracle/10.1.0.3/)
2) Installing ReportManager (for example on /opt/repmand)
3) verify if the Oracle VendorLib name on /root/.borland/dbxdriver is
the same of libclntsh.so* under lib root oracle installation. If is
not the same, create a link to the .so library or rename the VendorLib
name under dbxdriver. (for example, Oracle10g library name is
libclntsh.so.10.1).
4) Copy the TNSNAMES.ORA contents into the databasename connections
configuration, for example
&(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST =
hostname)(PORT = 1521)) )
(CONNECT_DATA = (SERVICE_NAME = ORATEST) ) )&.
On Linux is not a valid environment TNS_ADMIN=TNSNAMES.ORA path, so
is'n need create environment variables such as
ORACLE_HOME, ORACLE_SID, LD_LIBRARY_PATH and TNS_ADMIN.