Visual Studio 2010 RC Installation Issue on Windows XP machine

-
While trying to install VS 2010 RC on my windows XP sp3 machine, I was facing this issue that the installer wasn't able to install any of the components after it installed .Net Framework 4.0. Once I installed .NET Framework 4.0, it prompted me to restart the machine, and on restart nothing really happened (though the setup was expected to resume). I re-clicked the setup and still nothing happened.


So after trying to re-install VS 2010 a couple times, I found out the solution to the problem -
Display the language bar at the taskbar, right-click on it and choose settings. Then remove the hand writing support from the list. There is a bug in the RC for computers with touch screens.

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics CRM Server roles

-
Microsoft Dynamics CRM Server roles Recently I faced a situation where CRM was integrated with different other applications through Biztalk Server. Biztalk server made a lot of Server calls through connector. At peak hours, thousands of Biztalk instances were calling the CRM Services. That point of time, there was drastic impact on performance of CRM for end users. This type of situations can be avoided if proper planning is done during starting phase of implementation. CRM server roles were introduced with 4.0. The following table lists the various server roles that are available with Dynamics CRM 4.0.  The table also lists the Role Name used in the installation XML configuration file to choose the indicated role: Role Config Role Name Description SRS Data Connector SrsDataConnector Run reports. SQL Server SqlServer Installs the components required on the SQL Server where the Microsoft Dynamics CRM databases are maintained. Application Server ...
Read more

Using CRM Services to create or update records in large numbers

-
Recently, I implemented a plug in code which invoked auto creation of records from a contacts list (rather marketing lists based on MS CRM contacts) for my custom entity. The code worked well but it hanged whenever I considered a marketing list of more than 3000 contacts. The error logged read: Only one usage of each socket address (protocol/network address/port) is normally permitted. Basically, the error was thrown when the creation process exhausted the limit of socket connections allowed by the IIS and the SDK still polled for another connection and consequentially timed out after a certain number of records were created. A quick workaround for this is to change the following entries in the registry: HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort to 65534AndHKLM\System\CurrentControlSet\Services\Tcpip\Parameters\TCPTimedWaitDelay to be 30 The link : http://dmcrm.blogspot.com/2008/07/updating-records-in-mass-via-sdk.html also mentions a resolution of this by us...
Read more

Issues after Re-Naming MS CRM Servers computer/machine name

-
Currently I faced a scenario where the machine on which MS CRM 4.0 was installed was required to be renamed on LAN. My deployment had the SQL Server installed on another machine on LAN. After changing the MSCRM Server machine name, MS CRM browser stopped working and started showing error “SqlException: Login failed for user [Domain Name]\[New Machine Name] .” This error comes when the MS CRM server related entries in registry and database (that refer to the server name) have not yet been changed to the new server name This problem could be solved by 'Repairing’ the MS CRM 4.0 installation on the machine after renaming it. Go to the Control Panel -> Add or Remove programs-> Microsoft Dynamics CRM Server. Repair the installation. Repair installation internally performs the following actions: a. In the registry, ServerURL key value at HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MSCRM is updated with the new machine name (example: the value would be like “http:// :5555/MSCRMServices”...
Read more