MACINTOSH AND WIN 2003 server

1.  Are you receiving any other errors along with this one (like 12042?)  
2.  Is the share used only by mac's or do windows pc's use it also?
3.  check for file names longer than 31 characters....

1- NO
2- Yes windows users are using the same share.
3- There are more than 100000 files in my shared folders..I am sure they have files created more than 31 characters. Does this cause this kind of problem?

thanks
Cuneyt

the applefileprotocol (AFP) only allows up to 31 characters....

Here is a little neat program to find those pesky long file names:

http://www.dcsoft.com/ftp/longff.zip

Mazaraat,
Do you think this problem is related to it. I run that utility you have sent and looks like we have those files before we started getting 12052 eror. I event tried to open those files from a PC it didn't allow me to open but didn't create any event viewer error either. (in SYSTEM)
My system creates this messages starting from morning until end of work hours.. After the work I turned off all the MACs I have and one by one I turned them on and saved files to the server but couldn't create the error.

Yeah, I have specifically seen this error when the files were already located in the directory before AFP was installed and the share created.  Move those files or rename them at the server if you can't do it from a windows PC.  I don't think your going to be able to do it from a mac =(

I am looking into my open files window and confirm that none of these files are open. But system still creates the error log..Just now I went to a MAC, created an illustrator file with over 31 characters and tried to save to the server. MAC machine gave me error message and didn't allow me to copy since it is more than 31 characters.
Obviously files with more than 31 characters were created by windows users not MAC.

In order to not get the errors anymore you will have to change the names of the files to less than 31 characters from a windows PC or the server....use the utility I posted above to find them

Mazaraat
Error messages in the event viewer stops when MAC peopl loggs off. How do you relate it with long file name. Error logs are still being created even though nobody access to these long file named documents.
I get the errors As long as MAC people work in the system. As soon as they are off messages stops
For example yesterday between 0930am to 0530pm message repeated more than 200 times and cut it off until next morning.

When the mac users logs on and opens the share the files and folders are enumerated, this is where I believe your error is coming from.  The AFP (applefileprotocol) does not like files (or folders) with over 31 characters in the name.  Hence when a mac user logs on and USES the AFP by opening a share you get the error in the event logs.  You may have to wait till all the mac users are turned off, then make the change from the server.  If you can't rename the files look in controlpanel-admin tools-computer management-shared folders-open files-see if the files are opened by a person or process


Here is another question, have you recently added or upgraded any of the mac's to OS X?  (I think OS 9.3+ also has this)

No all of them are OS X.
And I do not understand how this happenned all of a sudden. We have those long file names created by windows users for so long.

Another possibility... your server could be running out of memory, but that is pretty far fetched...

I changed all the names.. and still having the same problem.

And today my server crushed when a windows user saving a mac file from one location to another.
Event id: 1003

Can you post the complete error, and any other errors or warnings thanks!

Event ID:4, Source: q57w2k, Type: Warning, Time: 5:18:57PM
"HP NC7781 Gigabit Server: The network link is down. Check to make sure the network cable is properly connected"
I already switched the Switch box that I plug the cable and also used bran new patch cable.

Event ID: 35, Source: WLBS, Type: Error, Time:5:18:57PM
"NLB Cluser 0.0.0.0:vCluster mode cannot be enabled due to paramater errors. All trafic will be passed through to TCP/IP. Restart cluster operations after fixing the problem by running'wlbs reload' followed by 'wlbs start.
I don't know what to fix about this. I didn't do anything about this.

Event ID: 6008, Source: Event log, Type: Error, Time:5:19:05
"The previous system shutdown at 5:09:48PM on 4/5/2006 was unexpected"

Event ID: 1285, Source: NIC Agents, Type: Eror, Time: 5:19:19PM
"NIC Agent: Connectivity has been lost for the NIC in slot ),port 2 (SNMP TRAP: 18006 in CPQNIC.MIB)"
I switched it to second NIC card on the server didn't help

Event ID: 1003, Source: System Error, Time:5:20:13PM
"Error code 00000050. parameter1 a7d13381, parameter2 00000000, parameter3 b7eccff4, parameter4 00000000."

I mentioned about Event ID: 12052 before. I get it all the time, Source: MacFile, type: Error
"A directory change notification was missed on voulme "Design Art"

Is this server part of a cluster or are the network cards configured for load balancing?  This might be a seperate issue.  If your using load balancing, redo your configuration then do a restart, see if those NLB errors get cleared up.

\Event ID: 35, Source: WLBS
As per Microsoft: "This event is probably logged because of incorrectly configured settings that are being read from the registry: in particular, IP addresses, IP subnet masks, or MAC addresses. Until this problem is corrected, this host will remain stopped and will not join the cluster".

I disabled network load balance service..
I still get 100's of event id 12052. This is so annoying. I read a lot of article but didn't help. I even uninstall NA from this server

richardleeds,

Are you using backupexec (ver 10d) and continuous file protection (CFP) ?

yes I was..... but I stopped that service as well.

Have you removed the mac share, restarted, then tried to recreate the share?

Yes i did that as well.

Mazaraat
It was CPS my friend. I uninstalled it and bingo..

thanks
Cuneyt

Sorry to hear that =(.  Its a great piece of software...when they finally work all the bugs out of it =)

They were going to give me hearth attack. I tried so many things, uninstalled service packs, securities, Norton...Now I applied them back again. Everything looks good so far..