社区
Sybase
帖子详情
Unable to load the requested database interface
jnsujihz
2003-04-01 08:25:01
Unable to load the requested database interface,please make sure both the interface and client software are properly installed.是不是我安装的不全啊?
...全文
96
1
打赏
收藏
Unable to load the requested database interface
Unable to load the requested database interface,please make sure both the interface and client software are properly installed.是不是我安装的不全啊?
复制链接
扫一扫
分享
转发到动态
举报
写回复
配置赞助广告
用AI写文章
1 条
回复
切换为时间正序
请发表友善的回复…
发表回复
打赏红包
MicroMouse
2003-04-01
打赏
举报
回复
重装一下看看。
pb连接SQLSERVER2005问题解决
pb连接SQLSERVER2005,提示如下错误:
Unable
to
load
the
request
ed
Database
interface
.Please make sure both the
interface
and client software are properly install
ed
. 解决办法:下载ntwdblib.dll然后将其copy到C:/WINDOWS/system32就行了.
ntwdblibaaaa
用pb连数据库提示如下错误:
unable
to
load
the
request
ed
database
interface
.plesase make sure both the
interface
and client software are properly insta?是什么问题?重装PB后问题还在。
ntwdblib动态库.rar
PB连接MSS SQL Server 提示
unable
to
load
the
request
ed
database
interface
,Please make sure both the
interface
and client software are properly install
ed
学习PB与SQL Server数据库的连接
学习PB与SQL Server数据库的连接
S7A驱动720版本
S7A驱动,7.20版本, Version history S7A OPC server and FIX driver for Siemens S7/S5 communication via Ethernet TCP/IP, MPI or Profibus Version 7.20 Date: 26.02.2007 Version history ================================================================================================================== Build 224 New Functions: Solv
ed
problems: - The setup program creat
ed
a wrong e-doc link in Windows start menu. Now the proper link to S7A.CHM will be install
ed
- From the S7A power tool it wasn't possible to open the online help file. Now it can be open
ed
and also the context-sensitive help works properly. - When the signal conditioning function "S&M" was us
ed
for a byte value, the driver wrote wrong values to the PLC. Build 223 : New Functions: - The number of support
ed
NetLinks has been increas
ed
from 4 to 64 - Communication error messages will be now display
ed
in the alarm history of iFIX. This helps to detect, trace and solve communication issues. - Support for MATRIX licence key add
ed
. This key does not require a special key driver. It simply ne
ed
s a PC and a windows version which supports USB ports. - When using the driver in conjunction with NetLink adapter, the licensing now can take place by a license code in the NetLink. In this case a separate licence key (dongle) is not ne
ed
ed
. Note: If the connection to the NetLink is disturb
ed
, the driver starts in demo mode, because it can't read out the licence code. If afterwards the connection to the Netlink can be establish
ed
, the driver automatically changes from demo mode to the licenc
ed
mode as long as the demo time has not yet expir
ed
. - Support for S7-200 with CP 243-1 was add
ed
. Solv
ed
problems: - Passing of invalid OPC Item IDs caus
ed
a memory leak of the driver's global memory. After the global memory was exhaust
ed
, the driver crash
ed
. - Writing of string values fail
ed
when using hardware options NULLTERM or SPACEFILL - Wrong OPC timestamp occur
ed
when driver was running in NIO Simulation Mode - The driver could crash when the driver was stopp
ed
(either by hand or when the demo time was expir
ed
) and in the same moment the NetLink connection was disturb
ed
. - Improvements on the seamless switching between primary and backup devices and vice versa. - The passing of invalid OPC Item IDs caus
ed
a memory leak in the driver's global memory. After the global memory was exhaust
ed
, the driver crash
ed
. - The writing of strings fail
ed
when using the hardware options NULLTERM or SPACEFILL Build 222 : New Functions: - The driver can now be register
ed
as a service with the local system account as the log-on account. For more information see the document "S7A_as_Service.PDF" on the installation CD . - The driver now switches "seamless" between primary and backup device and vice versa. Solv
ed
problems: - The field "Default Gateway" has been add
ed
to the NetLink's configuration property page - The string write from the OPC Server sometimes fail
ed
. This bug has been fix
ed
- After driver uninstall, not all of the S7A-relat
ed
registry entries were delet
ed
. Now the registry will be completely clean
ed
from S7A registry entries after uninstall. - The Netlink module generat
ed
trace messages to debug window. These trace outputs has been remov
ed
. Build 221 : New Functions: - The information field "Runtime Mode" has been add
ed
to the system statistic display. This shows whether the driver is running in the demo mode or in the licenc
ed
mode (with a valid key). - New control tag: "!RuntimeMode:S7A". A digital (i.e. DI) or analog (i.e. AI) block with the I/O address "!RuntimeMode:S7A" delivers the value 0 (in the F_CV property), when the driver is running in the demo mode, or the value 1, when the driver has found a valid key, and therefore is licenc
ed
. This function is also available via the OPC server
interface
. The same item-ID address format has to be us
ed
as with the tag-I/O address, thus "!RuntimeMode:S7A" - The information field "Device in use" has been add
ed
to the device statistic display. This shows which device (primary or backup-device) is currently active. This state can also be
request
ed
via the "!switch" control tag. A digital (i.e. DI) or analog (i.e. AI) block with the I/O address "!switch:
delivers the value 0, when the primary device is active and the value 1 when the backup device is active. For the place holder
in the I/O address the logical name of the driver device, which is
request
ed
, must be enter
ed
. Example: "!switch:D11" delivers the state of the driver device with the name "D11". This function is also available via the OPC server
interface
. The same address format has to be us
ed
for the tag-I/O address as for the item-ID, thus "!switch:
" - At the channel parameter dialog for the communicatiomn way "S7 TCP/IP" and "MPI/PB CIF", the combo box "Conn.Type" has been add
ed
, which now enables the selection of the connection types "PG", "OP" and "other". Until now, a PG connection was us
ed
. - In the device dialog of the communication way "MPI/PB CIF", the input fields "Rack:" and "slot no. of CPU" have been add
ed
. This extension now allows the connection to "external" Profibus- CPs (CP 342/443-5 or 343/443-5). The Profibus station address of the Profibus CP is stat
ed
in the MPI/PB address field. The rack and slot number of the S7-CPU must be stat
ed
in the corresponding fields. Please make sure that slot number of the CPU is enter
ed
and not of the Profibus-CP!! - The driver now supports the different date and time data types of the S7 PLC. See Topic "Hardware Options for OPC String and TX-Blocks to support S7 date and time data types" in the S7A online help for detail
ed
information. Build 220 : Solv
ed
problems: - The own address of CIF50 MPI/PB communication way was limit
ed
to 31. Now the limit is 126. - Bug-fix in PG-PC
Interface
(CP5611) communication way. Device could be disabl
ed
from polling, after CP5611 sent a specific sequence of communication errors. Build 219 : Solv
ed
problems: Improvements and new functions: - New Parameter "Max Gap (Bytes)" on Setup parameter property page "Advanc
ed
". This parameter defines the maximum address gap between an existing and a new block at which the driver automatically appends the new block to the existing. If the address gap is greater, then the driver creates a new data block. This functionality is active, when the data block auto create option is set on. - New Radio Button selection "Show Window" on Setup parameter property page "Advanc
ed
" The driver automatically opens its window which shows trace log messages useful for trouble shooting, when the "Yes" Radio button is on. - New HTML Help Build 218 : Solv
ed
problems: - Problems with datablocks which have a length between 180 and 200 bytes. - Unsufficient exception handling in S7AMemory.Dll caus
ed
blocking of driver and all other clients (WSACTASK, Workspace, etc.) which reads data from the driver. - Error in MIX Read function could cause blocking of data blocks Build 217 : Solv
ed
problems: - In configurations with data blocks which have a primary rate of zero (as fast as possible), it sometimes happen
ed
that write
request
s were "stuck" in the write queue. - Sporadic locks of data blocks after the driver was switch
ed
from the primary device to the backup device Improvements and new functions: - Improv
ed
error and timeout handling on communication faults. The reply timeout on the device configuration page can no longer be configur
ed
. Instead it will be deriv
ed
from the TCP/IP timeout value, configur
ed
on the channel configuration page. The value (in seconds) of reply timeout always is 1 second higher than the TCP/IP timeout. This ensures, that the logical read/write
request
(time-limit
ed
by reply timeout value) will not be cancell
ed
(by timeout) before the physical
request
(time-limit
ed
by TCP/IP timeout value) is finish
ed
regulary or through the timeout. - The NIO Simulation mode has been expand
ed
. If it is set "ON" the polling of data blocks will be disabl
ed
, due to which no communication errors will arise, as long as a PLC hardware is not connect
ed
to the driver. In this mode the iFix data base blocks reads the value of zero or respectively, the last value written to the driver`s output data area. - "!SyncPoll" and "!SyncSend" have been add
ed
to allow e.g. an
ED
A application to read/write a data block synchronously Build 216 : Solv
ed
problems: (06.06.05) - Reset of statistic counters fail
ed
Build 215 : Solv
ed
problems: (31.05.05) - An error in the OLE
interface
methods ReadValue ()and WriteValue() was correct
ed
. These functions can now be us
ed
for example,within the Excel program, to access data block values. - Datablocks stopp
ed
polling after an 'unknown error' was return
ed
by CP5611 Build 214 : Solv
ed
problems: - Syncronous reads/writes from concurrent OPC clients now work properly New function: - Performance has been improv
ed
, especially in configuration with a lot of short data blocks. - system, channel, driver and data block static display has been extend
ed
Build 213 : Solv
ed
problems: - No reconnect after the MPI/Profibus connection between CP5611 and the PLC was abort
ed
. - S7ADRV.EXE could crash on Multi Processor Systems or Systems with Hyperthreading when error messages (e.g. "
Unable
to connect to MPI station") were put to driver's log window from different threads concurrently. Build 212 : Solv
ed
problems: - The AGLink error code -1268 (Unknown error message of the PLC) caus
ed
a blocking of the device. Now the device will be clos
ed
and re-open
ed
to recover the error. - under very seldom conditions a AGLink error caus
ed
a crash of S7ADRV.EXE Build 211 : Solv
ed
problems: - Setup of TCP/IP parameters fail
ed
with error -510. Problem has been solv
ed
. - Problems in configurations with more than 8 devices within a channel have been solv
ed
- Import of CSV file from S7A Version 7.16 fail
ed
- Fail
ed
to read the AG State - Configuration of a backup IP address caus
ed
a driver crash when it tri
ed
to switch from primary to backup device Build 210 : New functions: - Communication way MPI/Profibus using Siemens CPs (CP5611, 5613) add
ed
- Communication way MPI/Profibus using Hilscher CIF50 PB add
ed
- Communication to "old" S5 series via TCP/IP add
ed
- The old Sentinel Keys will not support
ed
any longer - Check Box "Disable comm alarming" in datablock configuration allows to suppress the COMM alarms of Tags which addresses a driver datablock which is in communication error state. - Now the OPC server is OPC DA 2.05 complient Build 210 : Solv
ed
problems: - Under Windows XP the driver crash
ed
when the network cable was not connect
ed
to ethernet card and the driver start
ed
. - A communication error on a single device caus
ed
comm errors on all other devices of the channel Build 201 : Solv
ed
problems: - CSV Import/export works now even for the new communication ways. Build 200 : Solv
ed
problems: - Handle leakage when using asynchron read mode of OPC server. This problem was fix
ed
by migration to OPC server toolkit version 7.20 New functions: - The driver now supports additional communication ways (serial adapter, NetLink adapter and Siemens CPs (eg. CP5611). It's no longer a pure TCP/IP driver but a general driver for Siemens S7 which allows to connect via TCP/IP, MPI bus or Profibus using different
interface
hardware (CPs). Build 128 : Solv
ed
problems: - In big configurations with a lot of data blocks when a data block has been written it took too long until this data block was read back. Thus between the write and the read the clients (OPC or FIX) read the old data. Now after a write the driver reads the data block prioriz
ed
. Build 127 : Solv
ed
problems: - The addressing range for PLC's input area and output area has been extend
ed
from 0..255 bytes to 0..4095 bytes. Build 126 : Solv
ed
problems: - Errors in manual and automatic block write functions has been fix
ed
Build 125 : Solv
ed
problems: - Very fast consecutive analog writes to the same data block caus
ed
a crash of the S7ADRV.EXE process. This problem has been solv
ed
. Build 124 : Solv
ed
problems: - Different communication problems has been solv
ed
. - Design of message passing to driver window has chang
ed
to prevent the driver dead locks which occor
ed
under a very seldom conditions. Build 123 : Solv
ed
problems: - Changing of the IP-Address while the driver was running had no effect. This problem has been solv
ed
. Build 122 : New functions: - Now the devices within a channel processing in parallel mode - Add
ed
"Bytes per Second" to device and channel statistics - Logging of read/write
request
s/responses into a log file is now configurable for individual data blocks. File logging can basically be switch
ed
on/off at register page "advanc
ed
" in power tool's setup screen. - This version is already prepar
ed
to support the S7T
load
able
database
block which will allow to work with the S7 TIME and TIME_OF_DAY data types in iFIX
database
. - Shar
ed
memory management has been chang
ed
to fix problems with large configurations and multi processor systems. Solv
ed
problems: - In previous versions the S7 rack number had no effect. Now it will be mapp
ed
into the right bit positions of the "call
ed
TSAP" field when opening the ISO connection within the TCP connection. - An error in output simulations mode was fix
ed
. - An error in auto creation of data blocks was fix
ed
. Build 121 : Solv
ed
problems: - When the slot and rack number in the device setings has been chang
ed
, the new values wasn't us
ed
when the connection has been re-establish
ed
. Now the change of these parameters take place imm
ed
iately. Fix
ed
wrong display of Transmitt
ed
and Receiv
ed
counters of mission control's driver statistics Build 120 : Solv
ed
problems: - The OPC Server now supports read/write of Control-Tags (eg. !Send or !PollRate). Address syntax is equal to Tag I/O Address within FIX-
Database
. - Driver doesn't work when a channel with 8 devices was configur
ed
Build 119 : Solv
ed
problems: - Timeout value of channel template was not stor
ed
, thus it had no effect when a new channel was add
ed
. - IP-Address of device template was not stor
ed
, thus it had no effect when a new device was add
ed
. - To avoid duplicate Connection Numbers in Driver Device config, now these Connection Numbers are assign
ed
automatically. The "Connection No" Field in Powertool's device configuration dialog is no longer enabl
ed
for input but for displaying the assign
ed
Connection Number. - The driver devices are now limit
ed
to 8 per channel. - When running S7A driver on W2K without hardlock key (Sentinel or HASP) the Power Tool display
ed
an exception message box and the driver didn't start in demo mode. This problem has been solv
ed
. Build 118 : New function: - Additionaly to the Rainbow Sentinel Key the driver now supports new Aladdin HASP Key. It detects either Sentinel or HASP Key. Solv
ed
problems: - The OPC Server now supports String addresses Build 117 : Solv
ed
problems: - Now the Input Data Area of S7 can be read. That was not possible in build version 115 and 116. - The I/O address in data base builder now accepts inputs of adresses without blank between data area identifier and adress index (e.g. D11:Q1.7 or D11:I10.0). - Under a certain condidtion the S7ADrv process runs into a deadlock situation This problem has been solv
ed
. Build 116 : Solv
ed
problems: - Now the switching between primary and backup device can be configur
ed
and us
ed
. If the communication to the primary device fails, the driver automatically switches to the device configur
ed
as backup device. If the connection to the backup device fails, it switches back to the primary device. The switching even can be done by "hand" using a DI Block with I/O address "!switch:
. A F_CV value of 0 means primary device is active, F_CV value 1 means backup device is active. To change the active device just assign the corresponding value to blocks F_CV property. Build 115 : Solv
ed
problems: none New functions: - To make troubleshooting easier, the driver now allowes to log messages to a log file. To enable file logging, set the following registry key value to 1: "HKLM\Software\Intellution\Drivers\S7A\DriverDefaults\WriteLogToFile" By default this value is set to 0 which disables the file logging. The log file is nam
ed
S7ADrv.log and locat
ed
in the drivers default config file path. All messages dispatch
ed
to the driver server window will be logg
ed
in the file as well. Caution: The log file will "not" be delet
ed
and re-creat
ed
when driver starts. It's in the users responsibility to watch the size of the log file. If you enable the dispatching of debug level 1 to 3 messages, the log file can become a huge size in a short time!! Build 114 : Solv
ed
problems: - If SAC writes faster to the driver's image table than the driver can write to the PLC, after a while the write queue fill
ed
up to 100%. This version of the driver no longer queues write
request
s to PLC addresses which already in the queue, but uses the already queu
ed
request
by just replacing the old write value by the new value. - In configurations with more than 1 channel, the driver sometimes crash
ed
since This problem has been solv
ed
. - The Send and Receive counts in mission control was swapp
ed
. New functions: - Driver now runs with dongle RN-4BDNBH-B (S7A) and RN-4CKEBH-B (S7A+S7B) Build 113 : Solv
ed
problems: - Error in S7AMemory.dll caus
ed
problem in applications with very large configurations (where the shar
ed
memory "S7A_InputArea" exce
ed
ed
64k). The data type information stor
ed
in the Input Area was overwritten to WORD. Thus the SAC Task interpret
ed
the block values always as an integer no matter what data type was set for the data block in power tool. New functions: - none Build 112 : Solv
ed
problems: - CSV File import now works fine - When choos
ed
S7M 1.x compatible address syntax, the data type combo box was been set to a data type other that sav
ed
before. New functions: - The S7-TIME format now is support
ed
. Use a TX-blocks and the data type identifier 'T' in the Tag's I/O address to address a double word which contains a value in S7-TIME format (e.g. D11.DB100.DBT 10). Write is also possible. Build 111 : Solv
ed
problems: - Sometimes the CPU
load
rais
ed
to 100% when writing values. - Read/write of the last byte of a data block fail
ed
. - Block write in manaul or auto mode fail
ed
- In data block statistics sreen sometimes "stats error windows" occur
ed
because some error codes could not be found in AGLink_Error.txt file. New functions: - none Build 110 : Solv
ed
problems: - none New functions: - Add
ed
hardware options NULLTERM and SPACEFILL to control string write. Build 109 : Solv
ed
problems: - Sometimes driver hangs after communication fail
ed
. Occur
ed
when a lot of data blocks with a very short poll time has been configur
ed
and process
ed
. New functions: - none
Sybase
2,596
社区成员
25,614
社区内容
发帖
与我相关
我的任务
Sybase
Sybase相关技术讨论区
复制链接
扫一扫
分享
社区描述
Sybase相关技术讨论区
社区管理员
加入社区
获取链接或二维码
近7日
近30日
至今
加载中
查看更多榜单
社区公告
暂无公告
试试用AI创作助手写篇文章吧
+ 用AI写文章