MonitorWare Knowledge Base

by **Okcehc** on Mon Jun 09, 2003 3:44 am

"Unable to open ATK device for R access. Returning IO Status Block in Data. "

Could any give me an idea how to solve this problem ?

I know after that some application cannot lock file properly.

Thanks.

by **alorbach** on Tue Jun 10, 2003 9:25 am

Can you postthe whole eveng here?
Use the EventViewer Copy button, it will copy everything out in a formated way.

by **rgerhards** on Tue Jun 17, 2003 9:51 am

I found an article on this in the Microsoft Knowledge Base:

http://support.microsoft.com/default.aspx?scid=kb;en-us;130000

Here is one important part of it:

CAUSE
=====

These events indicate a problem with Performance Monitor not being able to
communicate with the Appletalk Protocol. These events are logged in the
Application event log while monitoring Appletalk or MacFile Server in
Performance Monitor when:

- SFM is not installed or started.

- The Appletalk protocol device or File SFM service is stopped.

- You have a bad network interface card (NIC) or network cabling.

- Macintosh seed routing is enabled in SFM with incorrect or conflicting
parameters.

MORE INFORMATION
================

There are two counters that performance monitor contains which allows a user to
monitor how SFM is behaving on a Windows NT server. In performance monitor, you
can select MacFile Server and Appletalk. These are represented by the
SFMCTRS.DLL and ATKCTRS.DLL files respectively.

Occasionally when viewing a event log on a Windows NT Server you may notice
events that have a source of SFMCTRS or ATKCTRS. If there are a large number of
events it could be an indication of problems with the SFM on the server.

HTH
Rainer

by **rgerhards** on Tue Jun 17, 2003 10:10 am

While doing some more research, I also found the following tip:

Explanation:
The AppleTalk Protocol is not installed or is not configured properly.

User Action:
In Control Panel, double-click Devices and check the Status list to verify whether the AppleTalk
Protocol is installed and started. Also, check the event log in Event Viewer for related messages.
If there are a large number of events recorded in the event log, there might be problems with
Services for Macintosh on the server.

This error, however, sometimes seems to occur even when Appletalk is completely removed. Some sources posted that checking & correcting the DNS setup could also solve it. I didn't find any indication that this was indeed succesful, but it may make sense to look into this issue - failing DNS name resolutions can always be a major trouble cause.

You may want to have a look at some articles on DNS that I wrote:
http://www.monitorware.com/Common/en/Articles/active-directory-and-dns.asp
http://www.monitorware.com/Common/en/Articles/Configure-Windows-DNS-for-Internet-Access.asp

Rainer

MonitorWare Knowledge Base

Win2000: 3001 atkctrs

Win2000: 3001 atkctrs

Google Ads

Who is online