are you logging to a text file? Is that error the entire contents of the file?

If you attempt to generate scripts do you get the same error?

You aren't dropping anything other than replication. You'll need to re-snapshot afterwads, but it replication isn't working anyway where is the harm?

Sorry, I'm a little confused as to why you are looking to have a separate database for reporting. What is the reason behind this?

Log shipping will not work based upon...

With the log shipped copy you are not going to be able to perform reporting functions as the database will not be available in that manner.

Why logship to the same...

If your server has 19GB of memory you should set the max server memory to 17GB

SQL could just be choking down on the OS causing the lock ups and issues...

Why not script out all of the replication objects, drop replication and then re-implement?

Have you enable extended logging? There should be more information than that.

Open up the maintenance plan, click on the reporting and logging button, in the window that opens up select...

Are you including logging for the maintenance plan? If so that detailed logging will provide a great deal more information to help identify the issue at hand.

You need to set the max server memory to cap the usage off at a certain point.

SQL will suck up as much as it feels it needs if you...

If this is a 32bit version of Windows have you also enabled PAE and AWE?

I do not believe that Windows 2003 SP1 is supported any longer, so you will need to move up to SP2 should you wish to continue to receive any support...

I have an RSS feed to http://blogs.msdn.com/sqlreleaseservices/default.aspx which contains the up to date information.

If 2000 check out http://www.sqldts.com

AWE should not be enabled on a 64bit system as the OS can handle the memory natively, additionally there is no need for the /3GB switch.

Check the max memory value...