Error

Mu online season 21 - grand opening

mercury71

Dedicated Member
Dedicated Member
Apr 3, 2006
155
3
44
im running 3.55 files

Now im getting a error in cruel dragon saying " 20:52:31 I/O error 32 - error on writing ErrorLog"
 

Far

tinmymouthpl0x
Staff member
Administrator
May 19, 2003
20,683
34
3,288
520
have you changed your date format to american, and the '/' to '-'??
 
Upvote 0

mercury71

Dedicated Member
Dedicated Member
Apr 3, 2006
155
3
44
yes the server has been running without probs for over 2 months now this has just happened
 
Upvote 0

mapadale

Guest
Delphi - I/O error 32

I/O error 32 means "SHARING VIOLATION", in other words: you're trying to access a file which is in use by some other process (in your program or "locked" by another application).

What this means, is when its trying to read/write information its finding that same information that its trying to read/write and gets confused to why its read/writing it again.

An easy way to solve this is by find your temp files folder and cleaning it, as with some programs that give the I/O error 32 this is where it stores the information before reading it from said program.

Another question though to ask, are you getting the I/O everytime you run CD?

Also do a search for the ErrorLog - Copy it and put it some where safe(remeber where you found it) and then delete the file from its location - Do that and then run CD again.
 
Upvote 0

Geordiehc

Mad Dog Geo
VIP
Jul 4, 2007
2,827
49
175
Redditch, UK
Delphi - I/O error 32

I/O error 32 means "SHARING VIOLATION", in other words: you're trying to access a file which is in use by some other process (in your program or "locked" by another application).

What this means, is when its trying to read/write information its finding that same information that its trying to read/write and gets confused to why its read/writing it again.

An easy way to solve this is by find your temp files folder and cleaning it, as with some programs that give the I/O error 32 this is where it stores the information before reading it from said program.

Another question though to ask, are you getting the I/O everytime you run CD?

Also do a search for the ErrorLog - Copy it and put it some where safe(remeber where you found it) and then delete the file from its location - Do that and then run CD again.
Nice research
 
Upvote 0

mapadale

Guest
Presumed u looked up the problem for him and spent your time helping him, so nice 1
Nah don't do things like that.

Help thats a nasty word please don't use it round me lol

It was easy once I knew platform for it.
 
Upvote 0