Connection interrupted - error 9268

Discussion forum about all things SqlBase.
Yvonne Grossmann

Connection interrupted - error 9268

Post by Yvonne Grossmann » 31 Jan 2013, 09:47

Hi,

we have installed SQLBase 11.7.0 at a customer. Before that we had SQLBase 11.5.2. The programs are in TD 5.2. The connection is via sqlws32. Usually all runs fine.

But practically every day one program suddenly looses the connection to the database and has to be killed. After this it can be restarted again, and it continues without problem.

Yesterday we had the situation that all programs on all client PC lost their connection at once. After this, they couldn't be restarted and brought the error "09268 GCI CCN Cannot connect" when trying to connect to the database. But it was possible to connect to the database locally from SQLTalk via sqlws32. Also restarting the database didn't help. Only after the restart of the server everything was fine.

The administrator said, that there was no problem in the network.

Well, the SQLBase 11.7.0 is installed on a server with Windows XP, which is probably not certified. I also had big trouble to load the database after the installation, since also SQLTalk often disconnected running locally on the server via sqlws32.

Now I'm afraid, that this problem continues. The client is quite angry, that since the installation of the new SQLBase there has been trouble almost every day.

Thank you and best regards

Yvonne

FRBhote
India
Posts: 2176
Joined: 09 Mar 2017, 05:32
Location: Hyderabad, India

Re: Connection interrupted - error 9268

Post by FRBhote » 31 Jan 2013, 11:38

9268 normally happens when there is a network error. Can you ping the server from the client?

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 31 Jan 2013, 17:26

Hi,

fortunatelly the error 9268 occurred only once yesterday. I didn't try to ping the server. But the network adminstrator said that there wasn't a network problem. It also was possible to access the programs on a volume at the server. They only couldn't connect to the database.

Now it happens several times per day that only on ore two programs are loosing the connection to the database. All other programs, also on the same client PC, are still running. I think, a network error would destroy the database connection of all running programs. It seems, that the problem can occur, when a bigger chain of transactions is being executed. But perhaps it only increases the probabality.

Could it really be a network error, when only the program with an open transation is affected, but the programs without activity on the same machine keep still connected and can continue later?

We really have to find a solution.

Thank you and regards

Yvonne

Mike Vandine

Re: Connection interrupted - error 9268

Post by Mike Vandine » 01 Feb 2013, 06:52

Hi Yvonne,

Can you please post your sql.ini file?

Perhaps you are not actually connected using WS32...

Does this only happen with one PC or with multiple PCs?

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 01 Feb 2013, 10:01

Hi Mike,

I've tried to upload the sql.ini, but I've always got the error message that the extension isn't allowed (I've tried to rename the file, but I've got this message with every extension). Therefore I've copied the files to the end of the post. But I think, there isn't another possibility than WS32.

It happens with several PCs, at least 5 or 6. Strictly speaking, it even happened on the server. Migrating the databases from 11.5.2 to 11.7.0 I've unloaded and loaded them. When I've tried to load one of the database files (database size 2 GB) into the 11.7.0 with SQLTalk, the session always was closed. I've solved the problem by copying the unload file from the customers server to my local machine und loaded it without problem into my test installation of SQLBase 11.7.0. Then I've unloaded some parts and could load the smaller unload files into the customers database. But after this, the database seemed to be OK. Well, this database has more than 10.000 tables, the most of them with only a few entries. But with 11.5.2 we never had a problem with it.

Thank you and best regards

Yvonne

sql.ini of the Client with TD 5.2:

;
; Unify Corporation 2008
; SQLBase INItialization file

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; This section is for the SQLBase Win32 database server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.

[dbntsrv]
dbname=ISLAND
dbname=SBTASK
ANSIJoinSyntax=1
centurydefaultmode=1
servername=Server1
autolocktable=0
batchpriority=0
cache=64000
dbdir=D:\SQLBase115

; The default value for readonly is 1, which allows use of "read only" and
; "read committed" (RO and RC) isolation levels. Uncommenting "readonly=0"
; will disallow use of RO and RC isolation levels.
;readonly=0

; To get process logging, specify a log file and display level.
;log=c:\dbsrv.log
;displevel=4


DBNAME=CONTROL,SQLWS32
DBNAME=MSGSYS,SQLWS32
DBNAME=MSGTEXT,SQLWS32
DBNAME=DATEN1,SQLWS32
DBNAME=MSGPRINT,SQLWS32
DBNAME=SICH1,SQLWS32
DBNAME=UPDATE,SQLWS32
[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32
;comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ws32]
ListenPort=2155

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlws32 REMOTE database using TCP/IP (WinSock)

[win32client]
clientname=Win32User
;clientruntimedir=C:\Programme\Unify\SQLBase115

[win32client.dll]
comdll=sqlws32
;comdll=sqlapipe

[win32client.apipe]
serverpath=Server1
;autostartserverpath=C:\Programme\Unify\SQLBase115\dbntsrv.exe

[win32client.ws32]
serverpath=server1,ow-srv-002/*




sql.ini of SQLBase 11.7.0:

;
; Unify Corporation 2008
; SQLBase INItialization file

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; This section is for the SQLBase Win32 database server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.

[dbntsrv]
dbname=ISLAND
dbname=SBTASK
ANSIJoinSyntax=1
centurydefaultmode=1

; The default value for readonly is 1, which allows use of "read only" and
; "read committed" (RO and RC) isolation levels. Uncommenting "readonly=0"
; will disallow use of RO and RC isolation levels.
;readonly=0

; To get process logging, specify a log file and display level.
;log=c:\dbsrv.log
;displevel=4

;
; SQLBase supports communicating through named pipes. Named pipes
; support Windows network authentication and allows a client running
; on the same machine to find a server without explicit configuration
; Options are:
; namedpipes=No ; 0 - Named pipes not enabled
; namedpipes=Yes ; 1 - Named pipes are enabled for local and remote access
; namedpipes=LocalOnly ; 2 - Named pipes are enabled for local access only. Remote access is denied
;
NamedPipes=LocalOnly
servername=Server1
autolocktable=1
batchpriority=0
cache=128000
dbdir=F:\SQLBase117
tempdir=F:\SQLBase117

DBNAME=CHARTER
DBNAME=DATEN1
DBNAME=MSGSYS
DBNAME=MSGTEXT
DBNAME=SICH1
DBNAME=UPDATE
DBNAME=CONTROL
DBNAME=MSGPRINT
AUDIT=GLOBAL,SBCCGLBL,C:\Programme\Unify\SQLBase117\,1000,1,1,,2,8
DBNAME=MSGTASK
[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32
;comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ws32]
ListenPort=2155

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlws32 REMOTE database using TCP/IP (WinSock)

[win32client]
; On 11.7 and above, if the CLIENTNAME is not specified, the computername
; will be displayed on the server. Also, the CLIENTNAME is not limited to 12 characters.
clientname=Win32User

; The transports option overrides the [win32client.dll] section.
; Possible values for transports are
;
; npipe,tcpv4,tcpv6,apipe
transports=npipe,tcp,apipe
clientruntimedir=C:\Programme\Unify\SQLBase117

;
; The [win32client.dll] used to have a list of communication .dll's
; to use for communication. Communication .dll's have been removed.
; This section is read and interpreted to be backwards compatibible.
; The transports parameter now supersedes it.
;
;[win32client.dll]
;comdll=sqlws32
;comdll=sqlapipe

[win32client.npipe]

[win32client.apipe]
serverpath=Server1
autostartserverpath="C:\Programme\Unify\SQLBase117\dbntsrv.exe"

[win32client.ws32]
serverpath=Server1,localhost,2155/*
Last edited by Yvonne Grossmann on 19 Feb 2013, 12:15, edited 1 time in total.

Mike Vandine

Re: Connection interrupted - error 9268

Post by Mike Vandine » 06 Feb 2013, 01:45

Hi Yvonne,

I don't think you are really using WS32 for your connection.

See the SQLBNEW.PDF document in the 11.7 version. Specifically the New Client SQL.INI Parameters section that talks about TRANSPORTS:

"The TRANSPORTS setting replaces the [Win32client.dll] section of the sql.ini file"

and

"To remain compatible with older sql.ini files, if the [Win32client.dll] section is present and no TRANSPORTS entry is present, the [Win32client.dll] will be used as it was before. If there is a TRANSPORTS section, it will be given precedence."

You have a transports statement in the client section of the server's sql.ini file, which specifies NPIPE as the first protocol (Named Pipes, very similar to Anonymous Pipes). I would suggest that you comment that line out and uncomment the [win32client.dll] section header and the comdll=sqlws32 in that section. In the [dbntsrv] section, change the NadmedPipe=Localonly to be namedpipes=No.

Please let me know if that helps with your stability.

Best regards,

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 18 Feb 2013, 15:44

Hi Mike,

I've changed the sql.ini as you described, but without success. The server sql.ini is now (and I've restarted the sqlbase, of course):

;
; Unify Corporation 2008
; SQLBase INItialization file

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; This section is for the SQLBase Win32 database server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.

[dbntsrv]
dbname=ISLAND
dbname=SBTASK
ANSIJoinSyntax=1
centurydefaultmode=1

; The default value for readonly is 1, which allows use of "read only" and
; "read committed" (RO and RC) isolation levels. Uncommenting "readonly=0"
; will disallow use of RO and RC isolation levels.
;readonly=0

; To get process logging, specify a log file and display level.
;log=c:\dbsrv.log
;displevel=4

;
; SQLBase supports communicating through named pipes. Named pipes
; support Windows network authentication and allows a client running
; on the same machine to find a server without explicit configuration
; Options are:
; namedpipes=No ; 0 - Named pipes not enabled
; namedpipes=Yes ; 1 - Named pipes are enabled for local and remote access
; namedpipes=LocalOnly ; 2 - Named pipes are enabled for local access only. Remote access is denied
;
NamedPipes=No
servername=Server1
autolocktable=1
batchpriority=0
cache=128000
dbdir=D:\SQLBase117
tempdir=D:\SQLBase117

DBNAME=CHARTER
DBNAME=DATEN1
DBNAME=MSGPRINT
DBNAME=MSGSYS
DBNAME=MSGTEXT
DBNAME=SICH1
DBNAME=UPDATE
DBNAME=CONTROL
AUDIT=GLOBAL,SBCCGLBL,C:\Programme\Unify\SQLBase117\,1000,1,1,,2,8
DBNAME=MSGTASK
DBNAME=TEST
DBNAME=TEST1
[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32
;comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ws32]
ListenPort=2155

; Win32 (Windows 2000, XP and Vista)
;------------------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlws32 REMOTE database using TCP/IP (WinSock)

[win32client]
; On 11.7 and above, if the CLIENTNAME is not specified, the computername
; will be displayed on the server. Also, the CLIENTNAME is not limited to 12 characters.
clientname=Win32User

; The transports option overrides the [win32client.dll] section.
; Possible values for transports are
;
; npipe,tcpv4,tcpv6,apipe
;transports=npipe,tcp,apipe
clientruntimedir=C:\Programme\Unify\SQLBase117

;
; The [win32client.dll] used to have a list of communication .dll's
; to use for communication. Communication .dll's have been removed.
; This section is read and interpreted to be backwards compatibible.
; The transports parameter now supersedes it.
;
[win32client.dll]
comdll=sqlws32
;comdll=sqlapipe

[win32client.npipe]

[win32client.apipe]
serverpath=Server1
autostartserverpath="C:\Programme\Unify\SQLBase117\dbntsrv.exe"

[win32client.ws32]
serverpath=Server1,localhost,2155/*

The problem remains the same: Sometimes one of the programs looses the connection to the database and has to be finished, while the other programs, also on the same PC, continue running. Usually it occurs when a certain number of data records has to be inserted into the database, but it happens with several tables. And it happens everyday.

I guess, there could be a physical problem with the hard disc, but it is a highly sophisticated virtual system on a raid.

What else can we do? It could become a show stopper, if we don't solve the problem.

Thank you and best regards

Yvonne
Last edited by Yvonne Grossmann on 19 Feb 2013, 12:14, edited 1 time in total.

Mike Vandine

Re: Connection interrupted - error 9268

Post by Mike Vandine » 19 Feb 2013, 07:38

Hi Yvonne,

Do you have a Tech Support contract with Gupta? Can you tell me your company name? That would certainly allow you some greater priority in resolving this problem.

This is not going to be an easy problem to solve unless you can give us a reproducible case that shows this happening and from the sounds of things this isn't going to be easy. So, some further questions:

Is the connection that is lost a little-used cursor connection? There might be some network connection timeout that is happening on that particular connection. That could explain why the other applications on the PC can continue.

Does this happen only with one PC or is it random?

Do you use isolation level RO or RC? If not, put in a specific line in the server section:

readonly=0

That will disable the history file.

Probably the next step is to put in a log= statement in the server section. This will capture that process activity statements. What you would look for is the error 9268 and then look further up in the log to see if there is another error message being shown just before this error is shown.

Best regards,

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 19 Feb 2013, 12:13

Hi Mike,

no, we haven't a Tech Support contract. Our company name is msg technologies gmbh. The problem ist, that we can't reproduce it. It happens during the work, usually several times per day.

It's definitively no little-used cursor connection. On contrary, it happens if one user is performing a lot of inserts. The first 50 or 100 work fine, and then, in the same function but the next transaction, suddenly the connection is interrupted, only for this one program. It can't be a timeout.

It happens on several PC.

We need the isolation level RO for other parts of the program and can't disable it.

I've started logging with level 2, not in the sql.ini, but in SQLTalk with SET PRINTLEVEL 2; and SET ACTIVITYLOG. I didn't want to restart the sqlbase.

The administrator is just examining an instability in the network. Not between the client and the database server, but between the database server and the (virtual) storage with the database files. Could this cause such a behaviour?

Thank you and best regards

Yvonne

ra_ga
Germany
Posts: 51
Joined: 06 Jun 2017, 13:10
Location: Munich

Re: Connection interrupted - error 9268

Post by ra_ga » 19 Feb 2013, 13:29

Hi,

maybe this could be a problem on PC-site. I get a similar error, when my PC gets in screen saver- or energy-safe-mode. Sometimes the machine lost the network-connection. After re-activation the database program crashes with no connection to the database.

best regards
Rainer

tfahey
United States of America
Posts: 99
Joined: 30 Mar 2017, 21:57
Location: La Crosse Wisconsin USA

Re: Connection interrupted - error 9268

Post by tfahey » 19 Feb 2013, 16:18

Perhaps try adding
clientcheck=1
to your sql.ini file.

We've used it for years to prevent odd disconnects on busy networks. This is especially important if your users are connecting via Citrix or TermServer.

However, I only see this error (#9268) on a first connection of a Process - not after a process has started. I see #9024 and #3804 / #3806 on jobs that are running, but become disconnected.

Tom Fahey

Mike Vandine

Re: Connection interrupted - error 9268

Post by Mike Vandine » 20 Feb 2013, 00:35

Hi Yvonne,

Well, the 9286 error basically states that a connection could not be made to the server. This normally happens when the server is not running. Another case is that the DB server is not 'listening' on the specific protocol (like TCP/IP). So, if there was a momentary problem with the TCP/IP and the SB server stopped listening, that could cause this problem as well.

Just to confirm, you say 'doing a lot of inserts'. Is this in one transaction, i.e. 'insert into ...' and the 50-100 rows get inserted or are there 50-100 insert statements. Something like this should never happen during the middle of the inserting of the multiple rows, but could conceivably happen with the multiple insert statements.

>>between the database server and the (virtual) storage with the database files. Could this cause such a behaviour?<<

That is certainly possible.

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 20 Feb 2013, 15:43

Hi,

to turn out the difference: I've gotten the error 9268 only one time. In this case all connections were dead, no new connect was possible, restarting the SQLBase didn't change anything, only a reboot of the server solved the problem. That was the only situation when I had an error with a number.

What is happing several times a day, is that many programs with a lot of sql handles are running on several machines. And just one program on one machine looses the connection. That is, all requests of all sql handles of this program run into an error. All other programs, both on the same machine and on the others, still continue running without problem.

I already know the problem with energy saving options of the PC, they all are disabled. But in this case usually all programs loose their database connection.

My error happens, when the user is still working with the program. It seems, that it happens when he has started a sequence of transaction, each containing some inserts und also some reads. I'm quite sure, that it only happens when a certain number of inserts have been performed.

Best regards

Yvonne

Mike Vandine

Re: Connection interrupted - error 9268

Post by Mike Vandine » 20 Feb 2013, 16:30

Hi Yvonne,

So the intermittent connection problem is NOT reporting an error 9268, even though that's the title of the thread... :(

>>That is, all requests of all sql handles of this program run into an error<<

So, what error are these handles getting? That is a critical piece of information!

Yvonne Grossmann

Re: Connection interrupted - error 9268

Post by Yvonne Grossmann » 07 Mar 2013, 15:37

Hi Mike,

it was a little problem to retrive the error numer of a crashed program, but now we have it: 3806 - Session closed/terminated. Thats really the first error, no other before. And after the first occurance every database request returns it. Almost every: one brought the error 9010 - Session closed.

The adminstrator said, that there were no network problems. And the database server also runs normally.

The problem occurs every day several times on distinct client PCs.

What can we do?

Best regards

Yvonne

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests