Can't save changes SQL 2008 Database

The fix is: Go to Tools | Options | Designers | Tables and Designers and uncheck the Prevent Saving Changes that require table re-creation option:

The wrong volume is in the drive. Please insert into drive" while clicking on link from Mail

I solved this problem by going to Device manager, removing the DVD-ROM drive (disable) I then had to restart. After I restarted I first went to the mail live program to see what kind of error I would get, no error. I then re-enabled the DVD-ROM drive via Device manager.

ESX and ESXi logfile locations

Location of ESX log files

You can see ESX logs:

• From the Service Console
• From the vSphere Client connected directly to the ESX host (click Home > Administration > System Logs)
• From the VMware Infrastructure Client connected directly to the ESX host (click Administration > System Logs)

The vmkernel logs (which log everything related to the kernel/core of the ESX) are located at /var/log/vmkernel

The vmkwarning logs (which log warnings from the vmkernel) are located at /var/log/vmkwarning

The vmksummary logs (which provide a summary of system activities such as uptime, downtime, reasons for downtime) are located at /var/log/vmksummary

The hostd log (which is the log of the ESX management service of the ESX) are located at /var/log/vmware/hostd.log

The messages log (which log activity on the Service Console operating system) is located at /var/log/messages

The VirtualCenter Agent log is located at /var/log/vmware/vmware/vpx/vpxa.log

The Automatic Availability Manager (AAM) logs are located at /var/log/vmware/aam/vmware_<hostname>-xxx.log

The SW iSCSI logs are located at /var/log/vmkiscsid.log

The System boot log is located at /var/log/boot-logs/sysboot.log

Location of ESXi log files

The VMkernel, vmkwarning, and hostd logs are located at /var/log/messages

The Host Management service (hostd = Host daemon) log is located at /var/log/vmware/hostd.log

The VirtualCenter Agent log is located at /var/log/vmware/vmware/vpx/vpxa.log

The System boot log is located at /var/log/sysboot.log

The Automatic Availability Manager (AAM) logs are located at /var/log/vmware/aam/vmware_<hostname>-xxx.log

Cluster warning for ESXi Shell for the Host has been enabled

In vSphere 5, you can enable both Remote SSH and the ESXi Shell for management of hosts from the vSphere Client and from the Direct Console User Interface.

 

These messages are shown as a proactive security measure that ensure that administrators are aware that remote access has been enabled for the server.

 

Disabling Remote SSH and ESXi Shell removes the messages from the host.

 

To disable these warnings: 

1. Select the ESXi host from the Inventory.
2. Select Advanced Settings from the Software menu.
3. Navigate to UserVars > UserVars.SuppressShellWarning.
4. Set the value from 0 to 1.
5. Click OK.

To disable these warnings using esxcli:

1. Connect to the ESXi host through SSH using root credentials.
2. Run this command: 
   esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 1

To enable these warnings using esxcli:

1. Connect to the ESXi host through SSH using root credentials.
2. Run this command: 
   esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 0

TSM Resettare le statistiche del recovery log

Se il reporter continua ad evidenziare l'errore "The max recovery log utilization is too high." nonostante sia stato eseguito un DB BACKUP allora probabilmente dovete resettare il counter dell'utilizzo del recovery log con il seguente comando:

Visualizzare lo stato del recovery log:
q log f=d

Resettare il counter:
reset logmaxutil



Visualizzare lo stato del recovery log:
q log f=d

Forzare aggiornamento ESX 3.5 da update manager

Controlla le porte utilizzate da update manager tramite vsphere client

Metti l'host in maintenance mode il comando che segue causerà il riavvio dopo l'aggiornamento

Collegati in ssh al server esx

Dai il comando: esxcfg-firewall -o "porta",tcp,out,dynamicupdates 

Es: esxcfg-firewall -o 9084,tcp,out,dynamicupdates

(questo consente al firewall di ESX di comunicare su quella porta)

Dai il comando: esxupdate -d http://"ip":"porta"/vci/hostupdates/hostupdate/esx/esx-3.5.0  --nosig update

Es: esxupdate -d http://172.16.0.100:9084/vci/hostupdates/hostupdate/esx/esx-3.5.0  --nosig update

Installazione Vmware tools su SLES 11 SP1

Creare una cartella:

mkdir /root/gpgkey

Con firefox andar all’indirizzo: http://packages.vmware.com/tools/

Salvare il file  VMWARE-PACKAGING-GPG-KEY.PUB dentro /root/gpgkey

Eseguire:    

rpm –import /root/gpgkey/VMWARE-PACKAGING-GPG-KEY.PUB

a questo punto aggiungere a zypper il repository (sorgente di software)

zypper addservice –type=YUM http://packages.vmware.com/tools/esx/ "versione vmware"/"versione SLES"/"tipo SLES  vmware-tools-collection

Verificare l'aggiunta del repository:  

zypper packages vmware-tools-collection

Procedere con l'installazione: 

zypper install –c vmware-tools-collection vmware-tools

controllare su VC o ESX nel summary del guest se viene riportata la scritta  "unmanaged"

NOTE:

"Unmanaged" is a valid state for VMware Tools, and indicates that some mechanism other than the classic VMware Tools "interactive/scriptable" installer engine is responsible for keeping the tools components "up to date".

This is what I would expect to see for the majority of newer virtual appliances being submitted for evaluation/validation through the VMware Ready Virtual Appliances Program.

Typically the "unmanaged" state is triggered by one of three cases:

VMware Operating-System Specific Packages (OSPs) served fromhttp://packages.vmware.com (nostro caso)

Open VM Tools

VMware Studio 2 supplied OSPs