a specified parameter is not correct: entityID

Similar Questions

• New-AlarmActionTrigger: A specified parameter is not correct

  Hello world

  I am trying to add a new alarm action to all my alarm vCenter definitions. Nothing complicated and because I'm lazy, I tried using PowerCLI for this. It's my little script:

  Get-AlarmDefinition | % {
    $_ | Get-AlarmAction | Remove-AlarmAction -Confirm:$false
      $_ | New-AlarmAction -Email -To '[email protected]' | % {
    $_ | New-AlarmActionTrigger -StartStatus 'Yellow' -EndStatus 'Red' -Repeat:$false
    $_ | New-AlarmActionTrigger -StartStatus 'Green' -EndStatus 'Yellow' -Repeat:$false
     }
  }
  

  When I run it, the action of the alarm and the two triggers are added. But when you add the alarm fires from "Yellow" to "Red", the following error occurs:

  New-AlarmActionTrigger : 04.07.2015 16:59:25    New-AlarmActionTrigger        A specified parameter was not correct. 
      
  At C:\Users\patrick\AppData\Local\Temp\bcfe38ed-7669-43dd-a588-7e88e59d70c4.ps1:4 char:8
  +         $_ | New-AlarmActionTrigger -StartStatus 'Yellow' -EndStatus 'Red' -Repeat:$fa ...
  +              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [New-AlarmActionTrigger], InvalidArgument
      + FullyQualifiedErrorId : Client20_AlarmServiceImpl_NewAlarmActionTrigger_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Alarm.NewAlarmActionTrigger
  

  Unfortunately I can not know what setting is not correct. The error occurs only for "Yellow" to "Red". No idea what is wrong or what did I miss?

  Thanks for the tips!

  Strange, as far as I know there is no beta 6R2 for now.

  Yes, it should work.

  You might find some clues in the vpxd.log.

  Otherwise, use Onyx to check what really happened to the methods.

• New-VM with OSCustomizationSpec, error "a specified parameter was not correct."

  I'm doing a script where I read a CSV file with settings to deploy multiple virtual machines. Now, I added functionality to get him to make sysprep with the help of OSCustomizationSpec and when I tested it work very well. After that, I made a few minor, such changes that added "-ResourcePool" and other things I can't remember unfortunately. Or at least I thought they were minor changes which should influence what negatively, but when I run it now I get error "a specified parameter was not correct." I found this thread saying it was a bug in the previous version, but that must have been fixed. I tried a workaround but I still get the same error. The script works well when I remove the "-OSCustomizationSpec" parameter, but it seems nothing wrong with the file I can manually deploy the virtual machines with the file OSCust from the GUI and the same models. And as I said, it worked well earlier when I used this setting. Any ideas on what "parameter", it's wrong?

  
  

  PSVersion: 4.0

  PowerCLI Version: VMware vSphere PowerCLI 5.5 Release 2 build 1671586
  

  
  

  The script starts the error message:

  New - VM: 2014-07-14 10:13:13 New - VM the functioning of the entity "model" failed with the following message is displayed: "specified a parameter was not correct. . ' spec.identity.userData.computerName '

  Script.ps1:141 tank: 6

  + New-VM-model $Template"

  +                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: NotSpecified: (:)) [new-VM], InvalidArgument)

  + FullyQualifiedErrorId: Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed, VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM

  And in the GUI:

  Task: Clone virtual machine

  Status: A specified parameter was not correct. spec. Identity . userData.c omputerN soul

  
  

  Below is the part of the script New - VM and OSCust:
  

  New-OSCustomizationSpec-name "PowerCLI" '

  -"Password" AdminPassword"

  -AutoLogonCount 0'

  -ChangeSID: $True '

  -Confirm: $False '

  -DeleteAccounts: $False '

  -Description "only for use with PowerCLI." "

  -FullName $Customer '

  -LicenseMode "NotSpecified" "

  «- NamingScheme «Fixed "»

  -NamingPrefix $VMName '

  OrgName - $Customer '

  -OSType 'Windows' "

  Time zone - 110'

  -'Persistent' type '

  -Workgroup 'WORKGROUP ' | Out-Null

  New-VM-model $Template"

  -Name of the $VMName '

  -VMHost $VMHost '

  -Store data $Datastore"

  -Map $Folder '

  ResourcePool - $ResourcePool '

  OSCustomizationSpec - PowerCLI | Out-Null

  Heck, I'm stupid, I think that it is Monday today!

  Just as you understand, it has something to do with the name of the computer.

  'spec.identity.userData ComputerName'.

  Or more precisely '-NamingPrefix $row.» Nu. Since this is the NETBIOS name, which can contain only letters, numbers and hyphens.

  As previously stated I'm stupid. I had $row. Defined as 'nickey_test01' and underscore name isn't a character allowed. This explains why the script already worked before when I created client VM. Guess I'll have to build in several controls in the script, for fool proof.

  Cheers for the help of Luke.

• The specified parameter was not correct: ".."

  Hello

  I am using VMware vCenter Converter Standalone to virtualize a few physical servers on an ESXi server.

  I installed ESXi 4.1.0 on a new server (quad core 2 processors, 48 gb of ram, a mirrored raid (where is the ESXi software) and a raid 5 for virtual servers).  I've already enabled 64-bit virtualization in the bios of the destination server.

  The first server I want to virtualize is a small server (Nothing mission critical).   The software main is executing is SpiceWorks.  I installed VMware vCenter Converter Standalone 4.3.0 Build-292238 on the source server.

  The error that I'm left with after you run the converter is:

  The specified parameter was not correct: ".."

  Let me guide you through the steps of how I get there.

  Launch of vCenter Converter

  Click on Convert Machine

  Under Select Source Type: Tension machine

  Specify the machine 'this local computer '.

  Next

  Select the Destination Type: VMware Infrastructure virtual machine

  Server: xxx.xxx.xxx.xxx

  user name: root

  password: password for root

  Next

  Name: leave the same...

  Next

  Select localhost.localdomain

  SELECT data store: Data1 (it was created on the raid 5 group, 860,75 1 GB of free space)

  Virtual Machine version: Version 7 of the

  Next

  Check the destination parameter... Check

  Let all the suggested default values / (go play with it more that one I get a working basis...)

  Next

  Summary (see bottom of post for summary)

  Finishing

  Special presentation...

  Then I get the error message

  The specified parameter was not correct: ".."

  The error message ends actually in times of double quotes

  If anyone has any suggestions, I would be grateful.

  Thank you.

  -

  ---

  Summary

  Information source system

  Source type: slot machine tension

  Name/IP address: the machine where works the VMware vCenter Converter Standalone server

  The CPU limit: None

  The network limitation: None

  Destination system information

  Virtual machine name: xxxxx

  Host/server: xxx.xxx.xxx.xxx

  Logged in as: root

  VM folder: None

  The host system: localhost

  List of resources: by default

  Power after the conversion: No.

  Number of processors: 2

  Physical memory: 3584 MB

  Network: Preserve County NIC

  NIC1 connected

  The VM network

  Type of disk controller: Preserve source

  Storage: The Volume of cloning-based

  Data configuration files store: Data1

  Customization of the destination

  Synchronize changes that occur during cloning: No.

  Install VMware Tools: No.

  Customize the guest operating system: No.

  Delete restore points: Yes

  Reconfigure the virtual machine: Yes

  in step 3 you can check to see if all volumes can be copied?  Just to make sure that it is a disk volume to move...

  The error should be something between the two tick marks, which is not double quotes.

  He complains that a value is null, rather than not null.  So, in step 3, make sure that nothing is missing.

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Converter Standalone 4.3.0 question - Get "the specified parameter was not correct" and no source listed volumes

  Sorry - hopefully an admin can move this to the correct forum. I could find no community forum labeled converter so no idea where to post this message.

  My first time trying to use the converter. Use the latest version of the Converter 4.3.0 to try a P2V by using the source computer. This is a laptop Dell D820 running Windows 7 Ultimate x 64 business. I chose the source machine and all the default settings. Destination product is VMware Workstation 7.x and target files are either local or to a port USB drive (tried both). In the last step, I get a yellow bar with the error "the specified parameter was not correct" "but the following quotes are empty and presume it suppose to say the name of the setting.» The only thing I see that is suspect is that if I click on change in section 'Data copy', the list of volumes and empty and assume that shouldn't be. The sample video to get advice on the use of converter on VMware support sites show a volume listed here. I tried the same approach on a completely different system under Vista SP2 and still no volumes appear so maybe it normal?

  No idea what I am doing wrong? I did export logs and watch and it appears no volume information has been captured (a lot of & lt; destroyed & gt ;) but even once, just guessing.) Any advice would be appreciated greadly.

  Thank you

  Don

  I had the same problem on a Win7 x 64 machine... There was no listed disk to convert.

  I managed to solve the problem by running the converter as an administrator. Right-click on the Desktop Converter icon and select run as administrator.

  The disks appears and you can select which can be the converter.

• Cannot add the vmkernel nic: a specified parameter was not correct. vSphere CLI + ESXi 4

  Hello. I try to add vmknic with frames in my distributed virtual switch.

  I read the vSphere command-line Interface Installation and reference Guideguide:

  "vicfg-vmknic - a-i DHCP"vmk5"

  I see the error message:

  Cannot add the vmkernel nic: a specified parameter was not correct.

  Vim.Host.VirtualNic.Specification.Ip

  What's wrong?

  I tried all the combinations of parameters with the same result.

  Ok! I've found a workaround.

  Since adding a vmkernel remote interface doesn't seem to work with DVS, I simply created one on a standard vSwitch and it then migrated to the DVS. And voila: the value 9000 MTU migrated intact with her! Here are the steps I followed:

  1. put the ESX host into maintenance mode - evacuate VMs manually if necessary

  2 remove the VMKernel iSCSI/NFS to the DVS interface

  3. create a standard virtual switch with no physical cards. He has no need to be a VMKernel VM Networking switch is fine. Make a note of the name you gave to the PortGroup created on the new vSwitch.

  4 using the remote control line, add the new interface vkernel specifying an appropriate jumbo MTU (9000) and the PortGroup on the standard new vSwitch. For example:

  esxcfg - vmknic.pl - Server

  If you get 3 answers, everything works. If you get failures, something has gone wrong. Go back and check that the interface is configured correctly using the command list esxcfg - vmknic.pl-.

  Enjoy!

  M

• From convert W2K3 comments led to "a specified parameter was not correct" error

  I converted a physical W2K3 server to VI3 (ESX 3.5.0 123623 and VC 2.5 119598) successfully.

  I was able to start the client afterwards, but nothing happened. Customer VI stated that the power has been a success but the machine did not come and showed again that power off.

  Making it the second and most times leads to an error message: "a specified parameter was not correct."

  I checked the hardware settings of the guest and has seen three ports series configured. I deleted the and tried to start it again. Again, the customer VI said that the power has been a success but the machine did not come and he always showed that power off and all suite trying generated this error again.

  I connected to the web interface and tried to start from there, but that has not worked, as well.

  I checked the disk space on the volume of SAN (there is an article stating that this error message appears when there is not enough space left to store the paging file in VC 2.0), but there are a lot of free concerts.

  .vmx:

  #! / usr/bin/vmware

  config.version = '8 '.

  virtualHW.version = "4".

  floppy0. Present = 'false '.

  NVRAM = "IN1CPTAPP005.nvram."

  deploymentPlatform = "windows".

  virtualHW.productCompatibility = "hosted".

  Tools.Upgrade.Policy = "useGlobal".

  powerType.powerOff = "default".

  powerType.powerOn = "default".

  powerType.suspend = "default".

  powerType.reset = "default".

  displayName = "IN1CPTAPP005."

  extendedConfigFile = "IN1CPTAPP005.vmxf".

  numvcpus = '2 '.

  scsi0. Present = 'true '.

  scsi0.sharedBus = 'none '.

  memsize = "4096".

  scsi0:0. Present = 'true '.

  scsi0:0. FileName = "IN1CPTAPP005.vmdk".

  scsi0:0. DeviceType = "scsi-disk" hard

  ide0:0. Present = 'true '.

  ide0:0. FileName = "".

  ide0:0. DeviceType = "atapi cdrom.

  ethernet0. Present = 'true '.

  ethernet0.wakeOnPcktRcv = "false".

  ethernet0.networkName = "internal129.230.149.x".

  ethernet0. AddressType = 'vpx.

  ethernet0.generatedAddress = "00:50:56:a6:26:d6."

  Serial0.present = "false".

  Serial0.yieldOnMsrRead = 'true '.

  Serial0.filename = ' / dev/ttyS0 ".

  serial1. Present = 'false '.

  serial1.yieldOnMsrRead = 'true '.

  serial1. FileName = ' / dev/ttyS1 ".

  serial2. Present = 'false '.

  serial2.yieldOnMsrRead = 'true '.

  serial2. FileName = ' / dev/ttyS0 ".

  guestOS = "winNetEnterprise."

  UUID. BIOS = ' 50 26 c2 cf 94 ea 50 - dd 6f 3A ff c3 e8 ec c0 EB.

  SCHED. CPU. Affinity = "all".

  sched.mem.Affinity = "all".

  scsi0:0. Redo = «»

  UUID. Location = "56 4 d 45 3 c this 36 28-4 b 69 93 d7 e1 93 a5 b5 cc.

  sched.swap.derivedName = ' / vmfs/volumes/48fc3709-252c5c10-6258-0014c26377c1/IN1CPTAPP005/IN1CPTAPP005-11a5b48b.vswp '.

  hostCPUID.0 = "00000005756e65476c65746e49656e69".

  guestCPUID.0 = "00000005756e65476c65746e49656e69".

  userCPUID.0 = "00000005756e65476c65746e49656e69".

  hostCPUID.1 = "00000f4800040800000064bdbfebfbff".

  guestCPUID.1 = "00000f4800010800000020010febbbff".

  userCPUID.1 = "00000f4800040800000064bdbfebfbff".

  hostCPUID.80000001 = "00000000000000000000000120000000".

  guestCPUID.80000001 = "00000000000000000000000120000000".

  userCPUID.80000001 = "00000000000000000000000120000000".

  evcCompatibilityMode = "FALSE".

  ide0:0.startConnected = "false".

  ide0:0.clientDevice = 'true '.

  guestOSAltName = "Microsoft Windows Server 2003, Enterprise Edition (32-bit)"

  .vmxf:

  Any ideas?

  I'm not sure why you're having the problem, but a quick fix is to create a new machine virtual just how you want with no disc, then join the VMDK virtual machine files that usually start.  The fire and see if it works.  It should be fine.  If so, you have some cleanup to do to get all the files in the same directory for the new virtual machine and removing the old VM.  Just pay attention do not remove your VMDK files!

• a specified parameter was not correct Vim.Host.VirtualNic.Specification.Ip

  Test network.

  ESX 3.5

  I want to connect ESX to Openfiler. When I try to add VMKernel I get err. : a specified parameter was not correct Vim.Host.VirtualNic.Specification.Ip

  For the IP, I entered the host IP. Clean install. No virtual machine in the inventory.

  Where to look?

  THX.

  You cannot use the same address IP assigned to the path of your host ESX service console - the VI Client is smart enough to know that the IP address is used - try using a different IP address on the same subnet.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful-

• Policy in the form of traffic-"a specified parameter was not correct."

  Hello.

  Here's a question for you all the gurus of cutting the code checking the syntax.

  I have a requirement to address the political shaping traffic outside esxcfg so orders need to complete in PS. I jumped directly to the Web of Alan site and found this wonderful example but when I copy / paste, change to vSwitch0 vSwitch1, it returns the message.

  Exception by calling 'UpdatePortGroup' with '2' or the arguments: "it was not correct to specified parameters.

  Vim.Host.PortGroup::Specification:vswitchId ".

  To: tank line: 22:28

  ++ $. mor UpdatePortGroup & lt; & lt; & lt; & lt; ($pgName, $portgrp) +.

  The URL for the code is here: http://www.virtu-al.net/2010/01/13/powercli-automating-traffic-shaping-on-portgroups/

  Any suggestions where I understand will be rewarded with points

  See you soon,.

  Darren.

  Hi Darren,

  I tried the code on my system and changed vSwitch1 to vSwitch0 and got the same error you did. Then I saw that you change to vSwitch0 vSwitch1 in two places in the code, line 3 and line 4. After that I changed both places it worked perfectly.

  Best regards, Robert

• Change from Thin to thick to help inflate the parameter-> specified is not correct

  Hello

  I wan to convert a VM disk of thin thickness.

  When "inflate" a disk from the data store, I get the message "a specified parameter was not correct."

  What to do to fix this?

  THX

  Please make sure you have machine virtual shutdown and deleted all the snapshot before proceed you to inflate. After you blow up if you see "the disc is not thin-provisioned." This means already changed my thick and in order to see the thickness that you will need to relaod the file vmdk by removing and joining the drive

• How to erase or correct an error loading RUNDLL that keeps Poppin ' up C:\ProgramFiles\ParetoLogic UUS2\USS.dll the specified module could not be found... error?

  How to erase or correct an error loading RUNDLL that keeps Poppin ' up C:\ProgramFiles\ParetoLogic UUS2\USS.dll the specified module could not be found... error?

  Hello

  Here is some information on this problem.

  The information contained in the link suggest you delete a scheduled entry, if it exists:

  http://www.utilitysoftwarereviews.com/how-to-remove-ParetoLogic-uusdll-error-message/

  You can also use this program (FREE Autoruns) to find:

  http://TechNet.Microsoft.com/en-us/sysinternals/bb963902

  See you soon.

• Removal of startup parameter error: the specified Service does not exist as an installed Service

  Hello

  I am currently removing two services in Autoruns, for the reason that they are highlighted, and that means that it no longer exists. However, I'm running into some trouble while he was trying to do, I get the following error:

  Removal of startup parameter error: the specified Service does not exist as an installed Service

  For diagnosis, I downloaded my log of Autoruns on OneDrive text file and you can view it by clicking here.

  Thank you

  Party of Lighthouse

  My research yesterday using Google yesterday suggested malware damage.

  Select Start, all programs, accessories, right-click right-click command promptand click run as administrator on the menu drop-down... Type cd\ and press ENTER. Type "chkdsk c:/r" without the quotes and press ENTER. Make sure you include the spaces indicated. Enter it when asked if you want to run chkdsk on restart the computer. Type exit, press ENTER, and then restart the computer.

  Please run the SFC system and say if she cannot fix corrupted files: http://support.microsoft.com/kb/929833

• Writable failing Volumes and Appstacks with "the device object parameter is not a valid object" at the launch of a .exe

  Previously, this error had been random between Appstacks and accessible volumes in writing, but became extremely coherent.   The full message is something like:

  C:\Program Files (x 86) \Mozilla Firefox\firefox.exe

  The device object parameter is not a valid object or is not attached to the volume specified by the file name.

  This accessible volume in writing will occur in a profile only (and UIA + profile) try to download and install the application, or what UIA only is only enabled when you try to run the installed applications.   It's almost as if the volume is not read/write permissions, but other information, such as the request for detailed information about the profiles are stored and used correctly.

  Running version 2.9

  Update - it seems that the question was of App - V Client being installed.

• the specified module could not be found

  To start my computer I get the following error: C:\windows\uhowegume.dll the specified module could not be found

  It is easy to get rid of the error message by doing something like disable the startup item in msconfig (if you can still find), but I suggest you fix the problem and difficulty not only the symptom of the problem by simply deleting the startup message.
  I would also not recommend you start digging in the registry to try to find the startup item and remove it unless you have a backup of your system or at least a backup of your registry, because there is no 'Cancel' or 'quit without saving changes' option in regedit.  If you make a mistake, that's all.
  These ideas relieve 'rapid' and sometimes risky of the symptom if they not even work at all, but they can't actually solve the problem.  Also, I'd be suspicious of ideas that begin with the words "try."  You don't need to try things, you need to fix things.  You don't need to try ideas that might work, you must do something that will always work all the time.
  Here are the detailed instructions that protect you and solve your problem in the 'right' way.
  There is very little. DLL files that should be loaded from the C:\WINDOWS folder and is not one of them.
  Describe your current antivirus and software anti malware situation: McAfee, Norton, Spybot, AVG, Avira
  !, Defender, ZoneAlarm, PC Tools, MSE, Comodo, etc..
  A "Cannot find...". ', ' Failed to start..., "Could not load..." ». "Might not work... "" Cannot run ""error loading... ". "or"specific module could not be found"message at startup is usually related to the malware that has been configured to run at startup, but the referenced file has been removed after a malware scan, leaving behind him a startup item or the registry entry pointing to a file that does not exist.
  It might be a removal of malicious software or an application not installed.  The entry may have a curious looking name since it was probably generated at random when the malware was installed. If you search your system for the referenced file, you may not find.
  Windows attempts to load this file but cannot locate because the file has been deleted for most probably during an analysis of the malware. However, an orphaned associate of remainders of startup parameter or registry entry and tells Windows to load the file when you start or connection.
  So you should delete the referenced entry Windows stop trying to load or run the file. It may or may not be included in the registry, but you can still find it.  Autoruns (see below) you get the elements no matter where it is.
  If you just locate and uncheck the item in msconfig, which disables the element but does not remove the reference to the element of false starting your computer.   The msconfig program is not a Startup Manager, that's a troubleshooting tool.  Disabling things in msconfig to put an end to the messages and think that your problem is solved is short-sighted and leave behind him a sloppy XP configuration.  Just disable the display of a start-up error message should not count as a 'solution' to the problem.
  If you are comfortable editing the registry, you can find and remove the reference directly from there or remove it using a popular third-party tool called Autoruns.  The problem can always be found in the registry well.
  Before making any changes to your registry by hand or with third-party tools, don't forget to first make a backup of the registry. There is no cancellation or exit without saving the option in regedit.
  Here is a link to a popular registry backup tool:
  http://www.SnapFiles.com/get/ERUNT.html
  You can use Autoruns to find the element of start remains little matter where he's hiding.  Autoruns does not install anything on your computer.  It will display all startup locations where the reference may be then you can turn it off or remove it completely.  Here is the download link for Autoruns:
  http://TechNet.Microsoft.com/en-us/sysinternals/bb963902.aspx
  Run Autoruns.exe and wait that he at the end of the filling of the list of entries.
  When the Autoruns is finished scanning your system, it will say "Ready" in the lower left corner.  Autoruns can be a little intimidating to first if you have never seen it before because it displays a lot of information.  You are really interested only a few sections.
  The problem is usually to start the system or the user startup entries, then click the connection tab and see if the startup item is there.
  Scroll through the list and look for a boot entry associated files in the error message.
  If you can't find on the connection tab, look in any tab.
  You can also click file, search to search for logon, or any tab for all or part of the name of the element.
  Right-click on the offending entry and choose Remove
  .  If you are not sure what it is, you can simply disable, restart and if the problem is resolved and then remove the offending entry.  If you don't see it in Autoruns, you may edit the registry and remove the item from your startup folder it.  Autoruns shall display the same information however.
  Given that systems currently has or has had an infection, follow up with this:
  Perform scans for malware, and then fix any problems:
  Download, install, update and do a full scan with these free malware detection programs:
  Malwarebytes (MMFA): http://malwarebytes.org/
  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
  They can be uninstalled later if you wish.
  Restart your computer and solve the outstanding issues.

  Do, or do not. There is no test.

  I decided to implement the points for a new puppy instead of a pony!

• Half-life 2 says failed to load the Launcher DLL specified module could not be found

  Failed to load the Launcher DLL:

  the specified module could not be found

  Hi Madoo17,

  Welcome to the community of Microsoft and thanks for posting the question. I've surely you will help find a solution on the issue.

  1. Once you get this error message?

  2. it worked before?

  3 did you changes to the computer before the show?

  Perform the steps:

  Method 1:

  Put the computer in a State of boot is a way to know which application is causing this problem.

  To help resolve the error and other messages, you can start Windows by using a minimal set of drivers and startup programs. This type of boot is known as a "clean boot". A clean boot helps eliminate software conflicts.

  Step 1:

  Put your boot system helps determine if third-party applications or startup items are causing the problem. If so, you need to maybe contact the manufacturer of the program for updates or uninstall and reinstall the program.

  Follow the steps in the link below to do the same thing:

  How to configure Windows XP to start in a "clean boot" State

  Note: After troubleshooting, be sure to set the computer to start as usual as shown here:

  Step 2: To configure Windows to use a Normal startup state

  After you have used the boot is a way to solve your problem, you can follow these steps to configure Windows XP to start normally.

  a. Click Start and then click Run.

  b. type msconfig and click OK. The System Configuration Utility dialog box appears.

  c. click on the general tab, click Normal Startup - load all services and device drivers and then click OK.

  d. When you are prompted, click on restart to restart the computer.

  Method 2: Use the (SFC) System File Checker tool.

  SFC system gives an administrator the ability to scan the files all protected to check their versions. If the System File Checker detects that a protected file has been replaced, it retrieves the correct version of the file in the folder cache (% Systemroot%\System32\Dllcache) or the Windows installation source files and then replaces the incorrect file. System File Checker verifies and repopulates the cache folder also. You must be logged in as an administrator or as a member of the Administrators group to run the System File Checker.

  Check out this link to do the same thing:

  Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)

  Hope this information helps. Please reply back with the State so that we can help you.