Error Dbms Is Not Supported In Your Current Installation
Contents |
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
links to the respective forums on SCN, or you can go to SCN and search for your product
Error 999 Dbms Is Not Supported In Your Current Installation
in the search box (upper right corner) to find your specific developer center. Forums Archive > PowerBuilder > General Discussion > "DBMS is not supported in your current installation" DBMS is not supported in your current installation 3 posts in General Discussion . Last posting was on 2007-12-07 21:32:19.0Z S. C. Peterson Posted on 2007-12-07 20:31:30.0Z https://groups.google.com/d/topic/sybase.public.powerbuilder.database/-OwRFv0fUtM Sender: 6e1.4759ad38.1804289383@sybase.comFrom: S. C. PetersonNewsgroups: sybase.public.powerbuilder.generalSubject: DBMS is not supported in your current installationX-Mailer: WebNews to Mail Gateway v1.1tMessage-ID: <4759ada2.6ef.1681692777@sybase.com>NNTP-Posting-Host: 10.22.241.41X-Original-NNTP-Posting-Host: 10.22.241.41Date: 7 Dec 2007 12:31:30 -0800X-Trace: forums-1-dub 1197059490 10.22.241.41 (7 Dec 2007 12:31:30 -0800)X-Original-Trace: 7 Dec 2007 12:31:30 -0800, 10.22.241.41Lines: 98Path: forums-1-dub!not-for-mailXref: forums-1-dub sybase.public.powerbuilder.general:210349 Article PK: 661027 PB: 10.5.1.(6684) Windows XP Oracle 10g 3-tier client/server/database PB http://nntp-archive.sybase.com/nntp-archive/action/article/%3C4759ada2.6ef.1681692777@sybase.com%3E application I am getting a "DBMS is not supported in your current installation" error attempting to connect to a database at the server tier. It worked in my development environment but has failed when I took it to a test environment. Below is the code and a section of the ini file. I tried the suggestion on Terry's techno-kitten.com site about using the appropriate db driver (pbo10105.dll). Put the dll in the location with existing PB dlls and replaced the live DBMS= line with the commented out one but still got the error. Any ideas would be greatly appreciated! ******** * CODE * ******** //Declare secondary local trans object. transaction ltrans_external_CACS //Read full path of ini. lstr_exteranl_ini = ProfileString(gstr_ini,"CACSG","CACSG_NET_INI_NAME", "") //Test ini path is valued. IF lstr_exteranl_ini = "" THEN //ERROR OUT Return -1 END IF //Create secondary local trans object. ltrans_external_CACS = CREATE Transaction //Value secondary local trans object. ltrans_external_CACS.DBMS = & ProfileString(lstr_exteranl_ini,"SQL","DBMS", "") ltrans_external_CACS.Database = & ProfileString(lstr_exteranl_ini,"SQL","DataBase","") ltrans_external_CACS.ServerName = & ProfileString(lstr_exteranl_ini,"SQL","ServerName","") ltrans_external_CACS.Lock = & ProfileString(lstr_exteranl_i
links to http://nntp-archive.sybase.com/nntp-archive/action/article/%3C48e66086@forums-1-dub%3E the respective forums on SCN, or you can go to SCN and search for your product in the search http://www.techno-kitten.com/PowerBuilder_Help/Troubleshooting/Database_Irregularities/database_irregularities.html box (upper right corner) to find your specific developer center. Forums Archive > PowerBuilder > Database > "DBMS Not Supported is not in current installation" DBMS Not Supported in current installation 12 posts in Database . Last posting was on 2008-10-03 18:46:48.0Z rfalagan Posted on 2008-10-02 15:43:43.0Z Sender: 313b.48e37b24.1804289383@sybase.comFrom: rfalaganNewsgroups: sybase.public.powerbuilder.databaseSubject: DBMS Not Supported in current installationX-Mailer: WebNews to Mail Gateway v1.1tMessage-ID: is not supported <48e4ec2e.5217.1681692777@sybase.com>NNTP-Posting-Host: 10.22.241.41X-Original-NNTP-Posting-Host: 10.22.241.41Date: 2 Oct 2008 08:43:43 -0700X-Trace: forums-1-dub 1222962223 10.22.241.41 (2 Oct 2008 08:43:43 -0700)X-Original-Trace: 2 Oct 2008 08:43:43 -0700, 10.22.241.41Lines: 12Path: forums-1-dub!not-for-mailXref: forums-1-dub sybase.public.powerbuilder.database:29518 Article PK: 311734 Deployed PB11.2 to Windows Vista Client ( for the first time )vs Sql Server 2000 Database. Using OLE DB driver. SQLCODE = 999 SQLERRTEXT = dbmSs not supported in curent installation I receive no errors in Windows XP. The appliaction runs fine on Windows XP Professional Client. Any suggestions. Thanks M. Searer Posted on 2008-10-02 16:00:34.0Z From: "M. Searer"
you treat as "under the covers" that you'll never have to look at. Row Changed Between Retrieve and Update This is a common and potentially frustrating message that is supposed to be used by the DataWindow's logical record locking. The intended use is that when another user has updated a record you have already retrieved, you won't be allowed to update the same record without re-retrieving it. While the WHERE clause in the Update Properties of the DataWindow defines the degree of logical locking implemented, and changing this property may make the symptom go away, changing it away from a more liberal level of logical record locking may be a quick fix that avoids understanding the problem and will likely cause other problems in the future. A change in the level of logical record locking should be made with careful planning and made universally. The basic cause of this message is: the DataWindow has generated an UPDATE statement the WHERE clause generated for the UPDATE statement fails to match any records on the database the WHERE clause is based on the option selected in the Update Properties dialog and on the values that the DataWindow believes are on the database Concurrency The first thing to examine when you get this message is to ensure that it doesn't actually reflect a concurrency issue. Things to check for concurrency conflicts include: other users other applications batch processes other windows or processes within a single instance of your application Triggers Insert or update triggers that affect columns used in the WHERE clause will cause this problem. If a DataWindow generates an INSERT or an UPDATE, the DataWindow will continue on with the understanding that the values that it last sent to the database are on the record in question. The next time that DataWindow generates an UPDATE statement to modify that record, it will use those values in the WHERE clause. If a trigger has modified those values, the WHERE clause will not match the record. Status Flags This is the most common problematic cause of this message that I've seen. If a value in the DataWindow is changed and the status is changed to NotModified through PowerScript functions, then the new value is going to be used as the row's original value in the WHERE clause. Other considerations should be given to programmatic manipulation of status flags, and the effect they have on the SQL that the DataWindow generates. The most common objective I've seen when developers try to manipulate status fl