Your Ad 
Here

Wednesday, January 14, 2009

Login Script Error line 530 char 4

Error:

User called in to say that he gets the error message when he logs on to the computer
The error message reads:
Script: \\serverdc2\netlogon\script.vbs
Line: 530
Char:4
Error: This network connection does not exist
Code: 800708CA
Source: Wshnetwork.removenetworkdrive

Fix:

Have them upgrade their wscript to 5.7

login on problems with sharepoint

If you have problems where you have to login to sharepoint then login to open documents try this:

IE>Internet Options>security>local intranet>sites>advanced

add

you domain name

Event ID 11 and 15 on VMware

VM is slow and freezes and picks up and freezes and picks up.

Caused by the Host with network problems to SAN.



Event ID: 11
Type: Error
Category: None
Source: Disk
The driver detected a controller error on \Device\Harddisk1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 03 00 68 00 01 00 ba 00 ..h...º.
0008: 00 00 00 00 0b 00 04 c0 .......À
0010: 03 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 05 9f 01 00 00 00 00 00 .Ÿ......
0030: ff ff ff ff 06 00 00 00 ÿÿÿÿ....
0038: 40 00 00 05 08 00 01 00 @.......
0040: dd 20 0a 12 42 03 20 00 Ý ..B. .
0048: 00 02 00 00 3c 00 00 00 ....<...
0050: c0 dc 05 89 50 b9 05 89 ÀÜ.‰P¹.‰
0058: 00 00 00 00 a8 86 06 89 ....¨†.‰
0060: 58 86 b5 89 00 00 00 00 X†µ‰....
0068: 28 00 00 00 00 00 00 00 (.......
0070: 01 00 00 00 00 00 00 00 ........
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

0000: 00680003 00ba0001 00000000 c004000b
0010: 00000103 00000000 00000000 00000000
0020: 00000000 00000000 00019f05 00000000
0030: ffffffff 00000006 05000040 00010008
0040: 120a20dd 00200342 00000200 0000003c
0050: 8905dcc0 8905b950 00000000 890686a8
0060: 89b58658 00000000 00000028 00000000
0070: 00000001 00000000 00000000 00000000
0080: 00000000 00000000 00000000 00000000



Event ID: 15
Type: Error
Source: Symmpi
Category: None
The device, \Device\Scsi\symmpi1, is not ready for access yet.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 0f 16 18 00 01 00 6e 00 ......n.
0008: 00 00 00 00 0f 00 04 c0 .......À
0010: 03 01 00 00 a3 00 00 c0 ....£..À
0018: b8 09 00 00 00 00 00 00 ¸.......
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 01 00 00 00 ........
0030: 00 00 00 00 08 00 00 00 ........
0038: 07 00 00 00 05 00 00 00 ........


0000: 0018160f 006e0001 00000000 c004000f
0010: 00000103 c00000a3 000009b8 00000000
0020: 00000000 00000000 00000000 00000001
0030: 00000000 00000008 00000007 00000005

CPU at 100 and 50 idle on VMware

Problem: Server runs at 100% CPU with app running/ and 50% CPU with app stopped. Restart does not resolve problem after restart CPU is at 50%. Both have been VMs in the new environment

Fix so far: Server shutdown and power back on.

Symantec Live Update Error LU1863

Error: U1863 There is not enough free disk space for LiveUpdate to operate properly. Please free up disk space on your computer and run LiveUpdate again
Cause: Proxy is blocking connection

Fix: Have to change Porxy settings in symanatec live update (http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2000071314574913?Open&docid=2005041311261648&nsf=ent-security.nsf&view=docid)

Reconnect errors in VIC

Errors when reconnecting:
1. Failed to install the virtualcenter agent service
2. Login Failed due to a bad username and password

Fix:
From the vmware console run

service mgmt-vmware restart
service vmware-vpxa restart

done Not enough storage is available to complete this operation error

Error message when you use a Windows Server 2003-based domain controller to join a Windows XP-based client computer to a domain: "Not enough storage is available to complete this operation"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;935744

To resolve this problem, increase the Kerberos token size. To do this, follow these steps on the client computer that logs the Kerberos event. 1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
Note If the Parameters key is not present, create the key. To do this, follow these steps: a. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos
b. On the Edit menu, point to New, and then click Key.
c. Type Parameters, and then press ENTER.

3. On the Edit menu, point to New, and then click DWORD Value.
4. Type MaxTokenSize, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Base area, click Decimal, type 65535 in the Value data box, and then click OK.

Note The default value for the MaxTokenSize registry entry is a decimal value of 12,000. We recommend that you set this registry entry value to a decimal value of 65,535. If you incorrectly set this registry entry value to a hexadecimal value of 65,535, Kerberos authentication operations may fail. Additionally, programs may return errors. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
297869 (http://support.microsoft.com/kb/297869/) SMS administrator issues after you modify the Kerberos MaxTokenSize registry value
7. Exit Registry Editor.
8. Restart the computer.

The case of the offline printer that is online

If you have a printer that is offline on the print server but you can ping the ip and the printer is online then check the SNMP settings and if it is enabled disable it the printer should be online again

Could not power on VM No swap file Failed to Power on VM

The following error occurred: Could not power on VM: No swap file. Failed to power on VM.
If you try to rename, delete or move the VM swap file, you get a "file in use" error.

Check the log file, should look something like this
Feb 01 15:03:31.486: vmx| DISKLIB-VMFS : "/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER-flat.vmdk" : failed to open (1048585): AIOMgr_Open failed. Type 3

Feb 01 15:03:31.486: vmx| DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode
Feb 01 15:03:31.486: vmx| DISKLIB-LINK : "/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER.vmdk" : failed to open (Device or resource busy).
Feb 01 15:03:31.486: vmx| DISKLIB-CHAIN : "/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER.vmdk" : failed to open (Device or resource busy).
Feb 01 15:03:31.487: vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER.vmdk' with flags 0xa (Device or resource busy).
Feb 01 15:03:31.487: vmx| DISK: Cannot open disk "/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER.vmdk": Device or resource busy (1048585).
Feb 01 15:03:31.487: vmx| Msg_Post: Error
Feb 01 15:03:31.487: vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/464420a7-a1e28a0d-6b66-0019bbd0c70a/MYSERVER/MYSERVER.vmdk' or one of the snapshot disks it depends on.
Feb 01 15:03:31.487: vmx| [msg.disk.configureDiskError] Reason: Device or resource busy.----------------------------------------
Feb 01 15:03:31.501: vmx| Module DiskEarly power on failed.
Feb 01 15:03:31.501: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
Feb 01 15:03:31.502: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
Feb 01 15:03:31.746: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Feb 01 15:03:31.746: vmx| VMX idle exit
Feb 01 15:03:31.757: vmx| Flushing VMX VMDB connections
Feb 01 15:03:31.763: vmx| IPC_exit: disconnecting all threads
Feb 01 15:03:31.763: vmx| VMX exit (0).
Feb 01 15:03:31.763: vmx| AIOMGR-S : stat o=1 r=0 w=0 i=0 br=0 bw=0
Feb 01 15:03:31.763: vmx| VMX has left the building: 0.

Kill the process
Run the following command on the Service Console to find out what process locks the swap file

ps aux | grep
If a rogue process locks the swap file, kill it and then try and start the VM.
Try this on every ESX server in the cluster.

Move the VM
Try to migrate the VM to a different ESX host and Datastore. It could resolve the lock on the swap file.

Check your LUN's
Check every ESX host in the cluster if all the LUNS are visible for the ESX host.
If a ESX host is missing a LUN, and the VM was running on that ESX host and LUN, the file is still locked after the ESX host lost connectivity to the LUN.
This was the case in our environment. After a SAN fabric problem, one ESX host was missing a LUN, and in a large environment you can easily miss that problem (12 node cluster, 40 LUNs')
Rescanned the LUNs, The rescan found the VM 'running'. Stopped the VM, and started it without a problem.

If everything fails
Shut down all the ESX hosts... This should definitely kill the file lock.

W2K Advanced 8 GB RAM Soft restart failure fix

Open boot.ini file and add the /noguiboot switch after the /PAE switch to fix the soft restart hang.

Paging addresses for phone carriers

AT&T: phonenumber@txt.att.net
T-Mobile: phonenumber@tmomail.net
Virgin Mobile: phonenumber@vmobl.com
Cingular: phonenumber@cingularme.com
Sprint: phonenumber@messaging.sprintpcs.com
Verizon: phonenumber@vtext.com
Nextel: phonenumber@messaging.nextel.com

where phonenumber = your 10 digit phone number

Trick to recover from Windows 2000 operating system file corruption

This method may be used for a scenario where the server storage is operational and free from issues but the operating system is showing signs of corruption. For example: When booting an error message is encountered similar to: "The following files is missing or corrupt \system32\ntoskrnl.exe".

Requirements: Windows 2000 Server CD, RAID installation drivers diskette, local NTADMIN password.

Boot from the Windows 2000 server installation media.
Press F6 to install RAID storage drivers
Once Windows 2000 Installtion CD is booted select "R" for Repair.
Then choose "C" to open the recovery console.
Select the system root from list and press Enter.
Supply local NTADMIN password.
Change to the system root directory. Example: CD \WINNT
Use "Dir $*" to locate most recent service pack uninstall directory.
Change in to the service pack uninstall directory. Example: CD $NtServicePackUninstall$
Change in to the 'spuninst' directory. Example: CD spuninst
Rename spuninst.bat to spuninst.txt
Run this command: "batch spuninst.txt"
Once complete type "exit" and press enter.
At this point the system should boot to the desktop. Logon and install latest Service Pack.
Reboot and run Windows Update and Reboot several times until all critical patches are applied
Done.

done Forgot ESX root password?

So, you forgot the ESX root password? Maybe you just need to change it after a staff change? To save yourself the hassle of reinstalling ESX on all of your hosts follow this simple process:

Use Virtual Center to Vmotion all of the VMs to other ESX hosts. (if you have a stand alone host then power down all your VMs)
Put the host in Maintenance Mode
Reboot your ESX host.
Physically go to the ESX console. You will not be able to use a remote console like WinSCP for the next few steps.
At the first menu type “a”
At the next prompt type “single”
After ESX finishes booting you will end up at a # prompt
Type “passwd” and enter a new password
re-type the new password again when prompted
Reboot the ESX server normally. ( just type “reboot” at the # prompt)
Don’t forget to take the host out of Maintenance Mode in Virtual Center.
Yes it’s that easy. It emphasizes how critical physical security is to your data center!