.NET Questions and Solutions

Most companies and firms these days are taking their businesses online. With so many people logging on to the internet for browsing, social networking and work, the chances of stumbling onto a website that advertises the products and businesses of companies is quite high. This gives even local businesses a chance to go global and become recognized. It’s also a good way to connect with customers and potential clients and keep them updated on new offers, changes and products.

A better method, however, is creating a landing page wherein details of whatever a company is involved in incorporated. Here, visitors can get all the information they’re looking for as well as being able to sign up or register with a site they’re interested in. A notable example is a Facebook landing page that links to a site. The page may images, videos, reviews and any other material deemed necessary to herd traffic to the said company’s website.

Symptoms
When you use the Microsoft SharePoint Migration Tool (Smigrate.exe) to try to restore aMicrosoft Windows SharePoint Services 2.0 Web site, the restore operation fails. You also receive the following error message:

Error getting manifest for http://localhost (fatal)Progress: An error occurred accessing your Windows SharePoint Services site files.This issue occurs after you use Smigrate.exeto back up a Windows SharePoint Services 2.0 Web site.
Additionally, when you rename the Backup.fwp file to Backup.cab to view the contents of the backup file, the Manifest.xml file is 0 bytes.
Resolution
This problem typically occurs on Windows SharePoint Server 2.0 Web sites if one of the following conditions is true:The Web sitecontains many lists.The Web site containslists that have large items.The Web site backup contains many files.Note Only file metadata is stored in the Manifest.xml file. The files are exported separately.
During the backup process, two contiguous memory blocks are required to create the Manifest.xml file. The memory blocks must be large enough to accommodate the manifest data. If one sufficient memory block is available to create the Manifest.xml file but a second sufficient block is unavailable, the copy operation fails silently. Then, a Manifest.xml file that is 0 bytes is created.

Symptoms
Consider the following scenario:You open a System Center Configuration Manager 2007 Service Pack 1 (SP1) consoleand use it toconnect to a site server that is running Configuration Manager 2007 without SP1.You open the Site Settings\Discovery Methods item, and then you double-click the Network Discovery item.In this scenario, you receive the following error message:

AdminUI.Console.dll
MMC has detected an error in a snap-in and will unload it. After you receive this message, you have the following options:Option 1: Report this error to Microsoft, and then shut down Microsoft Management Console (MMC).Option 2: Unload the snap-in. If you select option 2, and then you click OK, you receive the following error message, and the snap-in is shut down:

Unhandled Exception in Managed Code Snap-inFX:{6de537a5-7a1c-4fa4-ac3a-1b6fc1036560}The given key was not present in the dictionary.Exception Type:System.Collections.Generic.KeyNotFoundExceptionException stack trace:at System.ThrowHelper.ThrowKeyNotFoundException()at System.Collections.Generic.Dictionary`2.get_Item(TKey key)at Microsoft.ConfigurationManagement.AdminConsole.NetworkDiscovery.NetworkDiscoveryGeneralControl.UpdateUI()at Microsoft.ConfigurationManagement.AdminConsole.NetworkDiscovery.NetworkDiscoveryGeneralControl.InitializePageControl()at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()at Microsoft.ManagementConsole.PropertyPage.InternalInitialize()at Microsoft.ManagementConsole.PropertySheet.ProcessNotificationMessage(PropertyPageNotification pageNotif)at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
Resolution
The Configuration Manager 2007 SP1 console assumes that site servers have Active Management Technology (AMT) discovery information. However, such information is available only from site servers that are running Configuration Manager 2007 with SP1. When you try to obtain this information from a site server that is running without SP1, this issue occurs.

Symptoms
When you use the Stsadm.exe command-line tool to try to restore aMicrosoft Windows SharePoint Services 3.0 Web site on a computer that is runningWindows SharePoint Services 3.0, you receive the following error message:

The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space.
Resolution
This issue occurs if the computer that is running Windows SharePoint Services has insufficient free disk space that is available to host the restored Windows SharePoint Services Web site.This issue may also occur if the Windows SharePoint Services database has reached its maximum allowed size.

Symptoms
When you view subcollections on child sites, some subcollections may be shown in the Systems Management Server (SMS) Administrator console, and others may not appear. For example, one child site may have a specific subcollection, while another child site does not. Note that the missing subcollections are the subcollections that are created from a parent site, not those that are created locally to the child site.
Resolution
The SMS Administrator console only presents collections that are defined both in the Collections and Collection_SubCollections SQL tables. Because of timing issues, SMS Collection Evaluator and SQL Monitor may not correctly update both tables.

Symptoms
If you read Web pages from a site, an HTML page may be incomplete, or you may receive script error messages such as the following in Microsoft Internet Explorer (Programming) version 6.0:

Object doesn’t support this property or method
-or-

‘(object reference)’ is null or not an object It is also possible that an HTML page may be incomplete.
This occurs when you read Web pages from a site that uses all the following: Script in external files, for example, JScript (.js) filesFrames and script inside the frames that refers to variables or to methods that are defined in other framesHTTP compression to compress the HTML and the script filesHTTP headers that prevent the browser from caching the pages
The symptoms of this problem typically occur inconsistently and may appear random. Sometimes the error messages may appear when you first load the site. At other times the error messages may appear when you refresh the page.
Resolution
To work around this problem, you can do either of the following: If you use a Cache-Control: no-cache HTTP header to prevent the files from caching, remove that header. In some situations, if you substitute an Expires HTTP header, you do not trigger the problem.
-or-
Do not enable HTTP compression for the script files.