Skip to main content

Hello, everybody

Using runtime 9.2.5, sometimes it appears error 30/00 after an inactivity period in the computer. We use network units to conect computer to a server.

The O.S Server is Windows Server 2012 and the computer S.O. is Windows 10.

The error does not happen in other computers with different O.S.

I have verified opportunistick locking in the server and in computer.

Server: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters EnableOplocks = 0

W10 Computer: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MRxSmb\\Parameters OpLocksDusabled = 1

Any suggestion??

Thanks in advance,


#ACUCOBOL9.2.4

Hello, everybody

Using runtime 9.2.5, sometimes it appears error 30/00 after an inactivity period in the computer. We use network units to conect computer to a server.

The O.S Server is Windows Server 2012 and the computer S.O. is Windows 10.

The error does not happen in other computers with different O.S.

I have verified opportunistick locking in the server and in computer.

Server: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters EnableOplocks = 0

W10 Computer: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MRxSmb\\Parameters OpLocksDusabled = 1

Any suggestion??

Thanks in advance,


#ACUCOBOL9.2.4

Suggestion: Try upgrading to AcuGT v10.0.1, Our users who have been upgraded to Windows 10 have recently been reporting File Status 30,0 (ANSI 85) errors to us.  We have found that runtime v10.0.1 eliminates the FS 30 errors.

v10.0.1 works corrects the issue for user sites except for one user. It is not clear why it does not work for them, so I would be interested in other suggestions.

We started the upgrades because the runtime v9.1 C$FILESTATUS utility did not work well on Windows 10. Runtime v10.0.1 corrects that issue in all cases so far.)


#Windows10

Hello, everybody

Using runtime 9.2.5, sometimes it appears error 30/00 after an inactivity period in the computer. We use network units to conect computer to a server.

The O.S Server is Windows Server 2012 and the computer S.O. is Windows 10.

The error does not happen in other computers with different O.S.

I have verified opportunistick locking in the server and in computer.

Server: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters EnableOplocks = 0

W10 Computer: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MRxSmb\\Parameters OpLocksDusabled = 1

Any suggestion??

Thanks in advance,


#ACUCOBOL9.2.4

Hi everyone

It seems Windows 10 have changed the network units behaviours.

These units are disconnected after a period of time.

This link shows how this behaviour can been disabled.

community.spiceworks.com/.../1139165-windows-10-losing-mapped-drives

Hello, everybody

Using runtime 9.2.5, sometimes it appears error 30/00 after an inactivity period in the computer. We use network units to conect computer to a server.

The O.S Server is Windows Server 2012 and the computer S.O. is Windows 10.

The error does not happen in other computers with different O.S.

I have verified opportunistick locking in the server and in computer.

Server: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters EnableOplocks = 0

W10 Computer: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MRxSmb\\Parameters OpLocksDusabled = 1

Any suggestion??

Thanks in advance,


#ACUCOBOL9.2.4

Hi everyone

It seems Windows 10 have changed the network units behaviours.

These units are disconnected after a period of time.

This link shows how this behaviour can been disabled.

community.spiceworks.com/.../1139165-windows-10-losing-mapped-drives

Hello, everybody

Using runtime 9.2.5, sometimes it appears error 30/00 after an inactivity period in the computer. We use network units to conect computer to a server.

The O.S Server is Windows Server 2012 and the computer S.O. is Windows 10.

The error does not happen in other computers with different O.S.

I have verified opportunistick locking in the server and in computer.

Server: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters EnableOplocks = 0

W10 Computer: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MRxSmb\\Parameters OpLocksDusabled = 1

Any suggestion??

Thanks in advance,


#ACUCOBOL9.2.4

Angel,

Thank you! This solved our File Status 30,00 on the one user site for whom v10.0.1 did not make a difference.

Sal

Terms & ConditionsAccessibility statement