TechMania

SUMMARY
The Offline Files (CSC or Client Side Caching) cache and database has a built-in capability to restart if its contents are suspected of being corrupted. If corruption is suspected, the Synchronization Wizard may return the following error message: Unable to merge offline changes on \\server_name\share_name. The parameter is incorrect.

SOLUTION:
The Offline Files cache is a folder structure located in the %SystemRoot%\CSC folder, which is hidden by default. The CSC folder, and any files and subfolders it contains, should not be modified directly; doing so can result in data loss and a complete breakdown of Offline Files functionality.If you suspect corruption in the database, then the files should be deleted using the Offline Files viewer. After the files are deleted out of the Offline Files viewer, a synchronization of files may then be forced using Synchronization Manager. If the cache still does not appear to function correctly, an Offline Files reset can be performed using the following procedure:
1.In Folder Options, on the Offline Files tab, press CTRL+SHIFT, and then click Delete Files. The following message appears:
The Offline Files cache on the local computer will be re-initialized. Any changes that have not been synchronized with computers on the network will be lost. Any files or folders made available offline will no longer be available offline. A computer restart is required.Do you wish to re-initialize the cache?
2.Click Yes two times to restart the computer.

In Microsoft Exchange Server 2003 or in Microsoft Exchange 2000 Server, the information store is dismounted. Additionally, an event that is similar to the following event is logged in the Application log on a server that is running Exchange Server 2003 or Exchange 2000 Server:

Symptoms
Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 1159 Description: Database error 0xfffffd9a occurred in function JTAB_BASE::EcUpdate while accessing the database "".
Note The error code 0xfffffd9a translates to JET_errCheckpointDepthTooDeep.

CAUSE:

This issue occurs if the storage group that is related to the information store contains more than 1008 uncommitted Extensible Storage Engine (ESE) transaction log files. Each ESE storage group has a hard-coded limit of 1024 uncommitted ESE transaction log files. When the number of uncommitted ESE transaction log files in an ESE storage group reaches 1008, Exchange Server 2003 or Exchange 2000 Server starts to dismount all the information stores in the storage group. Additionally, the event ID 1159 message is logged in the Application log.

RESOLUTION
To resolve this issue, restart the Microsoft Exchange Information Store service. To do this, follow these steps on the server that is running Exchange Server 2003 or Exchange 2000 Server:
1.Click Start, click Run, type services.msc, and then click OK.
2.Click Microsoft Exchange Information Store Service, and then click Restart Service.
3.Quit the Services tool.

aofo: initialization failure...0xe000fed1: an error occurred querying the writer status

Details:Backup Exec 11d for Windows Servers version uses Microsoft Volume Shadow Copy Service (VSS) to perform backups of Exchange data. These backups initialize and run the Microsoft VSS provider and Exchange VSS writer which may not properly terminate after the backup job is complete. Once VSS has gotten into this state, backup jobs will fail with:
AOFO: initialization failure...0xe000fed1: an error occurred querying the writer status.
Possible workarounds include dismounting then mounting the Exchange databases using the Exchange Management Console or stopping and restarting the Microsoft Exchange Information Store service. In addition, the option of using Windows Backup (NTBackup) may be used as an alternative as well as it does not rely on VSS for Exchange backups.

Active Server Pages, ASP 0131 Disallowed Parent Path.
SYMPTOMS
When you use relative paths in include statements with Microsoft's Active Server Pages (ASP), browsing a Web page may return an error message similar to the following:
Active Server Pages, ASP 0131Disallowed Parent PathThe Include file '../' cannot contain '..' to indicate the parent directory.//, line

CAUSE
This is caused by disabling ASP's "parent paths" for a Web site or application while using relative parent paths in an include statement. Relative parent paths in include statements use the following form:

RESOLUTION
The best solution to the problem is to use absolute virtual paths from the root of the Web site instead of relative paths.For example, if you use an include file named "mycode.inc" at the root of your server, the virtual path would be "/mycode.inc." If you use the same include file in a virtual directory named "/includes" on your server, the virtual path would be "/includes/mycode.inc."The syntax example below illustrates how to implement virtual paths:

An alternative to using absolute virtual paths is to enable parent paths; however, this is not the preferred method.
This is accomplished for your default Web site by using the following steps:
1. Open the Internet Services Manager in the Microsoft Management Console (MMC).
2. Right-click on your Default Web Site and select Properties.
3. Click the Home Directory tab.
4. Click the Configuration button.
5. Click the App Options tab.
6. Click to select the Enable Parent Paths checkbox.
7. Click the OK button until you return to the MMC.

# posted by Tech Mania @ 10:50 AM 0 comments