We have a strange problem where a client is trying to load one of our upgrades onto a win 2000 server. Our upgrades just contain all records needed for transfering forms, programs etc. Has worked fine for years. The client keeps getting an error writing a record to SYSREPOSWINEXES. This same upgrade loads fine on other client's systems. I've rebuilt the upgrade, tried cut down version etc and its always this one record. The executable record is around 122,000 bytes. They're using OI32, 4.0.2. and the All networks driver 1.5. Tried changing to 2.1 but service pack only allows 1.5.

The error message is a write error, 1105 which is "Error number %2% returned during RCL request reply. There's also an 1102 in the error, which according to my list is "Resource in use error"

We've tried all sorts of things, rebooted the server, logged in as administrator, bashed it with a bit of 4x2 wood and nothing has helped.

Copied the source onto their system as well. When you try to compile the form in question (its a big one) it crashes as well.

Any suggestions would be appreciated.

Does STATUS() =2 help in any way? I think for OSWRITE etc this is Access denied by operating system. I don't know if its the same for a standard WRITE to a rev file though.

Paul,

Reminds me of some other posting not so long ago. Let me do a search for "64K"… …uh… …here it is: . But you might have seen it already.

- Oystein -

Thanks Oystein, That explains what is causing the problem. (I had to get someone else to look it up for me as I don't have works access)

I created a test record of 70K and tried to write it to SYSLISTS in the client's system and it gives the same error.

Revelation, is this a bug that can be fixed? ie: Cant write ]64K with service pack loaded.

Paul,

What kind of OS are you running on the workstation?  Also, are you running with the NT/2K Linear Hash Service and if so, what version?

Pat

Pat,

The workstation is Win98 connecting to a 2000 server via citrix. The server has ver 1.5 of the service running.

Paul,

The 1.5 NT Service was written before there was a 32-bit OI and was never stress tested on records ] 64K.  There are known problems in this area, of which Win98 seems to do the better job of encountering.  The 2.1 NT Service has resolved this issue.

Pat

Pat,

The link below seems to suggest that theres still a problem with ver 2.1. I need to be sure before we ask the client to fork out $$$.

Thanks

Paul

Hello,

Just as an FYI to the below information, this hasn't been determined if the problem is due to the Linear Hash service or due to a workstation/network configuration. Pat and I are still in testing.

However, the problem of accessing large records was resolved by configuring the 2.1 service to use both Named Pipes and TCPIP (or pure TCPIP). This is the mode we are currently working in and we haven't had any issues with it. Even when the problem is resolved, it is doubtful we will reconfigure the service to be just Named Pipes as everything is moving towards TCPIP.

[email protected]

SRP Computer Solutions, Inc.

]Pat,

]The link below seems to suggest that theres still a problem with ]ver 2.1. I need to be sure before we ask the client to fork out $$$.

]

]

]Thanks

]Paul

Paul,

You are correct that there is another issue related to writing 64k records using named pipes in the 2.1 service.  I have just figured out what the issue is and have a fix in the works.  Note that this was in fact only a named pipe issue and TCP/IP did not have the problem.

Thanks for the "prod" on this issue!

Pat

View this thread on the forum...