Ivan Versluis June 25th, 2008
I am running Ubuntu 8.04 LTS Desktop Edition 64bit edition and after I installed VMWare Workstation 6.04 Linux x64 edition I got the following error when trying to start my virtual machines sitting on a NTFS USB disk volume.
VMware Workstation unrecoverable error: (vcpu-0)
Failed to allocate page for guest RAM!
A log file is available in “/media/USB_DATA/NET-DC-01/vmware.log”. Please request support and include the contents of the log file.
To collect data to submit to VMware support, select Help > About and click “Collect Support Data”. You can also run the “vm-support” script in the Workstation folder directly.
We will respond on the basis of your support entitlement.
Please click OK and locate the vm file. Open the vmx file with nano or another text editor and add the setting below. Save the file and try to start the virtual machine again.
mainMem.useNamedFile = “FALSE”
This setting doesn’t use named-file - use for VMs on USB-disks or other slow disks
Windows: useNamedFile= “FALSE” causes memory to be backed by the host’s swap space.
Linux: useNamedFile= “FALSE” causes a hidden file to be created in a temporary directory, which is immediately deleted when you power off the VM
Tags: 64bit, allocate, Error, failed, linux, page, Ubuntu, vcpu-o, VMWare, workstation
Ivan Versluis June 4th, 2008
For weeks my local Infopath 2007 installation failed to open forms located on SPS server. See warning below.
InfoPath cannot open the following file: http://sharepoint/ChangeMgmt/Forms/abc.xml InfoPath cannot open the form. To fix the problem, contact your system administrator.
Form template: http://sharepoint/ChangeMgmt/Forms/solution.xsn. There is an error in the form’s cache. To correct the error, open the form again.
This was my solution is solving the problem. Before you start clean the Internet Explorer Cache!
For Windows Vista
- Locate C:\Users\%Username%\AppData\Local\Microsoft\InfoPath\FormCache2 and delete complete folder. If this fails than rename the subfolders to something else like abc and try again. I got a warning and the action failed if I did not rename the folder.
- Run C:\Program Files\Microsoft Office\Office12>INFOPATH.EXE /cache clearall
For Windows 2000/XP
- Locate C:\Documents and Settings\%Username%\Local Settings\Application Data\Microsoft\InfoPath\FormCache2 and delete the folder.
- C:\Program Files\Microsoft Office\Office12>INFOPATH.EXE /cache clearall
After these steps my Infopath forms opened again 
Tags: 2007, cache, Error, form, howto, infopath, office, solution, warning
Ivan Versluis April 27th, 2008
Couple minutes ago I initiated the remove of Active Directory and forced the demotion of a virtual machine domain controller. The domain controller exceed the 60day not being able to replicate and I was not able to get the replication working. It took me more than 90 minutes to troubleshoot and fix the problem. Since Windows 2003 there is option in the dcpromo tool to force the Active Directory removal.
| 1. |
By default, Windows Server 2003 domain controllers support forced demotion. Click Start, click Run, and then type the following command:
dcpromo /forceremoval
|
| 2. |
Click OK. |
| 3. |
At the Welcome to the Active Directory Installation Wizard page, click Next. |
| 4. |
At the Force the Removal of Active Directory page, click Next. |
| 5. |
In Administrator Password, type the password and confirmed password that you want to assign to the Administrator account of the local SAM database, and then click Next. |
| 6. |
In Summary, click Next. |
| 7. |
Perform a metadata cleanup for the demoted domain controller on a surviving domain controller in the forest. |
|
Reboot the server and cleanup the metadata with ntdsutil. I hate to use workaround like this, but there is not quick and dirty fix for me now. I am planning and testing to upgrade my Exchange 2007 server to SP1, but because the replication to the second dc did not take place for more than 60days the replication stopped.
One of the Errors on my primary domain controller. Demote didn’t work with force removal and option 3 also did not fix the problem when using the registry fix.
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 4/27/2008
Time: 5:18:39 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: NET-DC-01
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine’s views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2008-01-26 20:26:04
Invocation ID of source:
01dcf6c8-f6b8-01dc-0100-000000000000
Name of source:
e02a9b21-b7e0-4be6-9cc9-971b00325f65._msdcs.Networknet.nl
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the “repadmin /removelingeringobjects” tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
For more information check the knowledge base article.
Tags: Error, fix, guest, kb332199, machine, replication, virtual
Ivan Versluis April 25th, 2008
I tried to query my Windows 2008 Server roles by using the ServerManagerCmd.exe cmd tool and received nice red error as shown below.
C:\>ServerManagerCmd.exe -query
Error: Configuration was started by another administrator.That administrator must log in to complete that action before other administrators can install or remove additional features.
This tool opens a new horizon for me and other IT administrators but it didn’t work when I tried to use it for the first time. Google and Microsoft forums didn’t help so tried to troubleshoot myself. I read through the “Server Manager Scenarios Step-by-Step Guide” but this didn’t help me either. I decided to install the PoweShell feature manually and now I got a popup box that another process was in progress but I didn’t see it. I clicked yes and didn’t create a screenshot of this message, but this is how I resolved this issue.
Tags: Error, exe, query, servermanagercmd
Ivan Versluis January 29th, 2008
After installing CactiEZ 0.30 and you start using the Device Tracking Management (MacTrack plugin) area you may receive the following error when creating new site or device.
Error: save Failed.
This error is being generated by the Cacti system because there are no tables in the Cacti database.
Login on the console or with a ssh shell and execute the following commands
cd /var/www/html/plugins/mactrack
php database_upgrade.php
I have couple other issues after scanning a cisco switch, which I will need to follow up on the cactiusers.org forum. The device type list is empty in the newest version of CactiEZ and you will need to populate this yourself now.
Tags: 0.3, Cacti, cactiez, Error, failed, mactrack, save
Ivan Versluis January 25th, 2008
For weeks my lab Exchange 2003 cluster was down. The cluster was configured in a active passive configuration and only one server has been up for months; the second virtual guest node was shutdown. At some point I was not able to reach the Exchange 2003 mailboxes and I start to review the Eventviewer and Services on the active online node. System log contained around 100 4275 event id errors in the IIS Config catalog category. I manually tried to start IIS Admin service and even reboot the server but still without success to get the service up and running. Metadatabase was not changed in anyway.
Error parsing XML file. Reason: An invalid character was found in the content. Incorrect XML.
I went to C:\WINDOWS\system32\inetsrv and renanmed Metabase.xml file to Metabase.xml1. This is the file IIS uses for its configuration database.
I reviewed to eventlog to find out when this Eventid 4275 started. The first error was on 12 December.
The C:\WINDOWS\system32\inetsrv\History folder contains all previous XML Metadatabase history files.
I copied the one just before the error event and paste the file to C:\WINDOWS\system32\inetsrv. Rename the file to MetaDatabase.xml
Go back to Services MMC console and start IIS Admin and WWW service. Both started successfully. Start Cluster Administrator and bring to Exchange group online.
After weeks the Exchange 2003 cluster started to function successfully. Second note was updated and virtual machines were backuped.
Why did this happened? The only reason I was able to find is during the first day of the errors, there were couple of power outages and the IIS Metadatabase.xml file did became corrupt.
Tags: 4275, catalog, Error, iis config, metadatabase.xml
Ivan Versluis January 23rd, 2008
System Center Virtual Machine Manager 2007 is out for a while and I have been testing this product for two months now.
If you manually install SCVMM 2007 than Virtual Machine Manager 2007 Server Setup wizard may stop just before the installation is finished. I have also seen errors within the available SCVMM 2007VHD appliance from Microsoft’s website. Jobs are failing and Manager complaining about network paths incorrect.
Main reason why the setup fails is that the computername contains ‘-’ . For example I named the server REF-SCVMM-01 and the setup failed with error id 2917.
The network path was not found on the REF-SCVMM-01. Ensure that the share name provided maps to a valid local path, and then try the operation again. ID: 2917. Details: The network path was not found.
In the background PowerShell is not able to get the computername variable correct within the scripts it uses. In my case I renamed the computername to REF_SCVMM_01 and setup finished successfully.
Tags: 2007, 2917, Error, network path, Powershell, scvmm
Ivan Versluis January 23rd, 2008
If you installed wrong version of Hyper-V RC1 you may get the error below. I have experienced this with the binaries which I have download from MSDN subscriber website.
After you insert the integration components additions of Hyper-V the installations stops with this error.
An error has occurred: One of the update processes returned error code 61658.
The error has to do with the certificates being used by the setup procedure. The certificates have expired November 2007 and you are still using the Hyper-V CTP version, Hyper-V RC1 has no more MSU installation after the server has been installed. For more info go to this link at MSDN blogs.
Go to this link and download the correct version named 6001.17119.071210-1916_amd64fre_Server_en-us-KR1SXFRE_EN_DVD.iso.
Tags: 61658, Error, Hyper-V, integration components, msi
Ivan Versluis January 17th, 2008
After you deploy the DPM agent on a Windows Server 2003 and you try to create new protection group the wizard may come back with the following error message.
Make sure you read the following Knowledge Base article 940349 and install the VSS patch.
Tags: 2007, 31008, DPM, Error, prerequisite
