Entry for September 28, 2005

It was tough to leave Patni because of the emotional attachment I had with the company I worked for 2.5 years. But life goes like this.

I have started working for my new company in Orlando which is the Software Div of Florida Hospitals.

I am thankful to all of my friends who kept me motivated to achieve all my success. Special thanks to Mr. Anurag Bhargava who forced me to believe that I can leave Patni...:), to the Raj who guide me how to do that in a matured way and to my wife for her efforts and taking care of all my email conversation with the consultants .

Comments - Migrated from Yahoo 360, where I had my blog.

(5 total) Post a Comment

Anu
Offline

dada I didnt forced u but I was disappointed (every month two times when u get ur pay slip).... no hard feeling PATNI ... dada I am happy for u and those 22$ first pay cheque is mine and will be most valuable $22 for me ....

Wednesday September 28, 2005 - 04:01pm (EDT) Remove Comment

Sure wo 22 aapke amanat hai hamare paas

Wednesday September 28, 2005 - 04:04pm (EDT) Remove Comment

Anu
Offline

aamanat yaane dene ko vichar nahi hey kya :(

Thursday September 29, 2005 - 12:49pm (EDT) Remove Comment

amaanat to amaanat hoti hai use kahi bhej kar amaanat me khayaanat nahi karenge

Thursday September 29, 2005 - 01:48pm (EDT) Remove Comment

Anu
Offline

yaane dada aap bhi patni jesa karoge ... dikhaoooge ! deoooge nahi .....

Thursday September 29, 2005 - 10:33pm (EDT) Remove Comment

Comments

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart. Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel. I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances. RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs. 25 Best Blogs of 2009 25 Best Blogs 2008 25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...

Laksha

Search This Blog