MSI Debug Logs : Trouble shoot the Installer problems

The applications which I am currently working gets installed in the system using MSI Installer. I am getting some problems after i installed and restart the system. I usually create log files to track out any problem that i am getting in my application. But these log files did not help me for figuring out some problem regarding installation. Then I heard from some of my friends that there are MSI logs are available in the system through which we can easily figure out installation related problems.
But for getting that log files we need to enable them before installing the application.
Here is the path to enable that
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
in some operating systems you dont find Installer folder, then you can create by right clicking and selecting new. Once you have above path in your system you can proceed with installing your application. So that OS will log all the errors and actions that are appearing in system while installation.
Once installation is completed you can get MSI log files in %temp% folder of system with starting file name as MSI...

Take logs...track problems

Windows Vista USB Detection problems

I am working on some application that are actually run from USB devices. What happened was when i am using that application in windows vista operating system in VMware, Vista was unable to detect the USB device . I tried so many times by plugging and removing. Then I asked my friend google,he routed me to some pages where i found that vista having some problems in detecting USB devices. We may need to install service packs and some fixes in order to avoid these problems. So i proceeded with installing service packs and fixes. Then it started working fine.
One more excited thing i got in this experiment that is when i created vista using latest VMware version 6.5 then the vista started detecting the USB devices with out installing service packs..
some confusions are here is whether the problem is in vista or VMware. Anyway finally i ended up with some solutions. I am just sharing my experiences here so that if somebody get same problems they can solve as per above two methods....
links that would help for same problems are here http://support.microsoft.com/kb/941600

VMWare : 64 bit guest in 32 bit host

Hi, I had a requirement where i want to test one application in 64 bit VMware. I tried creating 64 bit VMWare on 32 bit host. After i spending so many hours i came to know that my machine does not support 64 bit VMwares.
For avoiding these situations you can download one EXE from VMWare website which tells you whether your machine supports 64 bit VM OS or not. Once you know the result then you can proceed creating that.

Here is the link http://www.vmware.com/download/server/drivers_tools.html

Simply download for your respective platform and check...
funny programming...

VMWare problems

I am using VMware for testing some of my applications. When i see VMware i really got excited as its allowing us to see OS inside OS. But some times got irritated because its not allowing me to drag a file from base OS to guest OS and internet connection problems.

when you see such problems in VMwares, first thing you need to do is go to VM tab in VMware and click on Install Vmware tools. So that it will install some of the files that will repair most of our problems.I think this option would work for your most of common problems.

Enable Administrator account in windows vista

I came across the need to log in as administrator in windows vista . But vista is not allowing me to do that as by default the administrator account is disabled and we need to manually enable that for logging .
Its very simple to enable that by running a small command. Below is the what i am talking about.
Steps:

• Open the command prompt through administrator mode by right clicking choosing run as administrator
• Now type the command below "net user administrator /active:yes" Then say enter.
• You will be getting message saying that the command completed successfully.
• Now log off. You could see option to log in as administrator. You can set password as well once you log in first time.

silly troubles..funny solutions...

Schedule and Run a SSIS package

• SQL Server 2005 is bit different from SQL Server 2000. In SQL Server 2000, you can create the job and run it without problem. In SQL Server 2005, we need to follow some steps for creating job.
• The job creator account should have the roles of Sysadmin, SQLAgentuser, SQLAgentReader, SQLAgentOperator and job needs to be run under proxy account
• The steps are follows as below.
• Creating Account:
  SQL Server Management Studio- >Highlight Security->New Login->Give login user and password and database is your selected database
• Server roles: check sysadmin
  User mapping: your database
  Msdb database:Iinclude SQLAgentUserRole, SQLAgentReaderRole, SQLAgentOperatorRole -> click on OK.
• Creating Proxy Account:
• In Object Explorer, expand a server.
• Expand SQL Server Agent.
• Right-click Proxies and select New Proxy.
• On the General page of the New Proxy Account dialog, specify the proxy name, credential name, and description for the new proxy. Note that you must create a credential first before you create a proxy if one is not already available. For more information about creating a credentialCheck the appropriate subsystem for this proxy.
  On the Principals page, add or remove logins or roles to grant or remove access to the proxy account
• Creating Credentials:
• In Object Explorer, expand Security, right-click Credentials, and then click New Credential.
• In the New Credentials dialog box, in the Credential Name box, type a name for the credential.
• In the Identity box, type the name of the account used for outgoing connections (when leaving the context of SQL Server). Typically, this will be a Windows user account. But the identity can be an account of another type.
• In the Password and Confirm password boxes, type the password of the account specified in the Identity box. If Identity is a Windows user account, this is the Windows password. The Password can be blank, if no password is required.
  Click OK.
• Job Creation,Scheduling,Running:
• In SQL Server Management Studio-> SQL Server Agent -> Start. Select job ->New Job>give name
• Then select steps tab-> New Step->give name
• Type: SQL Server Integration Service Package->Run asmyProxy->Package source: File System.
• Select your file through browse->YourPackage.dtsx->Say OK->then schedule and run it