Error Error 1124

That's a good call. Thanks cj.
Does anyone have any ideas how I could create a report of what is running on the machine at any moment in time? So I could set it running on Tuesday evening and get the results on Wednesday morning, hopefully with the tell-tale signature of the culprit?
 
I know that "sharing is caring" and all that sort of hippy-dippy stuff but, in the world of databases... shared = bad.
 
Agreed. Although after more investigations it's unlikely that anyone actually has it mapped as a drive.
 
We've discussed software but not so much the hardware. Given that it's running Server 2003 I assume this is a pretty old box. Is it even in warranty anymore?

Have you tested the disks with a vendor utility? Could you relocate the DB to different storage and see if the 1124s go away? Can you replace the disk controller?
 
It's a crap box. It's not even running 64bit Progress. It's a massive issue. It needs to be rectified but as always the people holding the purse strings don't agree. Ideally I'd love to go to a nice new linux box. But that will never happen because the IT Manager has an aversion to *nix.
The disks have been tested by support and are clear.
I stumbled across procmon yesterday, so the plan is that I will RDP on at about 1am on a Weds and start it running and watch until something goes bang, then can use the log files from that to see if we can investigate what's going on. It's just a shame the logfiles get so big so quickly. On my local machine it went to 70MB in about 2 minutes. lol
 
Process Monitor is a good tool. Be sure you have the latest version (3.05 as of today). Also, to control file size and location:
  • Filter for the process(es) you care about, assuming you know what they are. E.g. create filters like PROCESS NAME IS _mprosrv.exe, PROCESS NAME IS _mprshut.exe, etc. If you're not sure that you know a comprehensive list of processes then you can use a different relation operator, like PATH BEGINS WITH C:\myDLCdir. You can use multiple filters if you want. But understand the rules; they are documented in the help. Basically, if you have multiple filters with the same value on the left side of the relation they are ORed together. Multiple filters with different values on the left side of the relation are ANDed together. For example if you used the filters above, it would filter for events where (( process name is _mprosrv.exe OR process name is _mprshut.exe ) AND ( path begins C:\myDLCdir )). Let me know if I didn't explain that well.
  • Select "Drop filtered events" from the Filter menu. That will keep stuff you don't care about out of the log and make it much smaller. Understand though that if you're new to the tool you may not yet know what you want and what you don't. So try without it at first.
  • Don't use the paging file; that will limit you. Before you start your capture, select File | Backing files and redirect the output to a .pml file somewhere on your file system (not the DB storage obviously, if you can help it).
I guess you know that you need administrative privilege to run Process Monitor. Also, it can be a bit more challenging on older OSes. On Vista/Server 2008 and later, PM ties into the ETW subsystem and is pretty responsive. On prior OSes (XP, Server 2003/2003 R2) it can take a little while to do things like stop a capture and save a file. That's a pain as it starts capture immediately when you run it. You can get around this by launching it from an elevated command prompt with "procmon -noconnect". You will notice that by default some activity is filtered out by default, including paging file I/O and activity in the System "process".

I'm no expert with PM but I've used it a bit. Let me know if you need any help. Also, these videos (PM part I, PM part II) on Channel9 might help you as well. Good luck.
 
Cringer said:
It's a crap box. It's not even running 64bit Progress. It's a massive issue. It needs to be rectified but as always the people holding the purse strings don't agree.
Click to expand...

I certainly hope this isn't prod. But even if this is just a dev box, this kind of resource waste is unconscionable. Some people have no money for good infrastructure but seemingly unlimited resources for fighting preventable fires.

Cringer said:
Ideally I'd love to go to a nice new linux box. But that will never happen because the IT Manager has an aversion to *nix.
Click to expand...

Your company should have an aversion to this IT Manager. He/she is a troll and has to go. Not wanting to learn is no excuse for limiting an entire organization's deployment options.

Cringer said:
The disks have been tested by support and are clear.
Click to expand...

And the disk controller? And RAM?
 
lol thanks for the comments folks. Yes the box is production. The mind really boggles. Part of the issue we've had is that at the moment we are part of an organisation where the IT specialists have no understanding of what Progress is. We are getting rid of them in the next couple of weeks thankfully. Next job is to get the server sorted. It's ridiculous. We're happily using 11.2.1, but what's the point?
 
As of my experience most people have no understanding of basic IT knowledge - which resources are available on a computer and how they work together and are used by software. Not even sepaking of people that understand how RDBMS' work - not mentioning Progress here at all. For most IT specialists, I had the pleasure to meet over the years, a RDBMS is just files and the data users enter are just magically ending up somewhere in them.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top