What happened to the settings for background processing? In MCMS 2001 they were in the SCA.
Changes have been made to move more information about background processing into the MCMS database. Based on this, the decision was made that the best management interface would be through the Microsoft SQL Server™ agent.
From the MCMS 2002 CHM:
Using MCMS Background Cleanup
When you install MCMS or upgrade to MCMS 2002, the Database Configuration Application (DCA) sets up background processing by inserting stored procedures into each database and configuring a Microsoft SQL Server Agent job to run these stored procedures.
If you rerun the DCA and select an existing database that already has an associated Microsoft SQL Server Agent job, DCA does not change that job.
If the selected database does not have an associated Microsoft SQL Server Agent job, DCA creates one.
The name of the Microsoft SQL Server Agent job is BGP-<database name>.
You can use SQL Enterprise Manager to modify the Microsoft SQL Server Agent job information. For example, you can change the following defaults:
The job is configured to run at 1 a.m., daily.
The job does not delete expired postings. You must enable this option.
When the background processing job starts, stops, completes, or encounters an error, a text-only log file is written. The log file is located in the Microsoft SQL Server Agent directory.
When using background processing, note the following issues:
Background processing will not start if the Site Deployment is running. An error message is written to the Event Log.
If you stop Microsoft SQL Server, Microsoft SQL Server Agent is also stopped. When you restart Microsoft SQL Server, however, Microsoft SQL Server Agent is not restarted automatically. You must restart Microsoft SQL Server Agent manually.
If the DCA is installed locally and Microsoft SQL Server is installed on a remote computer, the DCA cannot start Microsoft SQL Server Agent. You must start Microsoft SQL Server Agent manually.
For more information about Microsoft SQL Server backup and restore, see
http://go.microsoft.com/fwlink/?LinkId=9559.
[Back to Top]
Topic: Error Message: "'ConfigWindow' is undefined"
When I try to open the SCA and click on CONFIGURE button it throws an error. The Error window says 'ConfigWindow' is undefined and when scrolled back to previous error messages it says' access is denied'.
What can I do to resolve this problem?
Answer
This can happen if the DCOM security settings are misconfigured. Please try the following steps:
- Start\Run: DCOMCNFG.exe
- Navigate to Component Services\Computers\My Computer\right-click, Properties\Default COM Security tab\Access Permissions\Edit Default
- Add your user to the user lists
- Reboot the machine
[Back to Top]
Topic: Error message: "The user name you supplied is not a local administrator"
When I open the Server Configuration Application (SCA) I get an error that the user is not an administrator on the local machine. But the current user is actually a local administrator. What should I do?
Answer
This error can happen when the Internet Information Server (IIS) server side includes are not correctly installed. Please follow the hints in the MCMS SP1 readme file to reinstall the IIS server side includes.
[Back to Top]
Topic: Failed to get Virtual Web Server Collection
When I try to open the Web Panel in the SCA I receive an "Unexpected Error! Failed to get Virtual Web Server Collection" error and "Access is denied. (-2147024891) " in details.
Answer
This indicates a permission problem on the registry. Please download regmon from www.sysinternals.com and check for access denied problems (ACCDENIED).
Correct all problems listed to correct the problem.
[Back to Top]
The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information presented after the date of
publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO
WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or
other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents,
trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
© 2004 Microsoft Corporation. All rights
reserved. |