If you receive an error message similar to "Unable to add data connection. Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified" and you are looking for a solution to the same, then you have come to the right place.
The following helped me solve this problem:
Install the following from the Microsoft SQL Server 2008 Feature Pack, August 2008 site:
1) Microsoft SQL Server Management Objects, and
2) Do a repair install on Microsoft SQL Server System CLR Types
This should solve the problem you are having.
Happy debugging!
Tuesday, May 25, 2010
Monday, October 12, 2009
Visual Studio 2005 debugger does not attach to application
This issue happens with IE8 as the browser used for debugging. IE 8 has a feature called Loosely-Coupled Internet Explorer (LCIE) (http://www.microsoft.com/windows/internet-explorer/beta/readiness/developers-existing.aspx#lcie) which results in IE running across multiple processes.
Older versions of the Visual Studio Debugger get confused by this and cannot figure out how to attach to the correct process.
To overcome this issue, you need to disable the process growth feature of LCIE by following the steps below:
1) Open RegEdit
2) Browse to HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a DWORD under this key called TabProcGrowth
4) Set TabProcGrowth to 0
If you run into the same problem on Vista or newer, you will also need to turn off protected mode.
Following the above steps should resolve your issue.
Regards,
Paras Wadehra
Older versions of the Visual Studio Debugger get confused by this and cannot figure out how to attach to the correct process.
To overcome this issue, you need to disable the process growth feature of LCIE by following the steps below:
1) Open RegEdit
2) Browse to HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a DWORD under this key called TabProcGrowth
4) Set TabProcGrowth to 0
If you run into the same problem on Vista or newer, you will also need to turn off protected mode.
Following the above steps should resolve your issue.
Regards,
Paras Wadehra
Wednesday, February 25, 2009
Response.Redirect does not work in AJAX callback functions
If you can't seem to use Response.Redirect in UpdatePanel's AJAXified callback function, add the following in your web.config file in the appropriate place:
<configuration>
<system.web>
<httpmodules>
<add type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" name="ScriptModule">
</httpmodules>
</SYSTEM.WEB>
</configuration>
Try now, and it works!
--
Paras Wadehra
<configuration>
<system.web>
<httpmodules>
<add type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" name="ScriptModule">
</httpmodules>
</SYSTEM.WEB>
</configuration>
Try now, and it works!
--
Paras Wadehra
Labels:
AJAX,
ASP.Net,
Paras,
Response.Redirect,
UpdatePanel,
Wadehra
Wednesday, November 12, 2008
Failed to access IIS metabase.
If you get an error saying "Failed to access IIS metabase." when you try to browse to a .Net App in the browser, it means that you installed IIS after you had ASP.Net installed.
To fix this problem all you need to do is run this command (on a command prompt) on your computer: %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
This will reinstall ASP.Net for use with IIS and in most cases fixes the error.
For reference, the full error that I received was as follows:
Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904
To fix this problem all you need to do is run this command (on a command prompt) on your computer: %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
This will reinstall ASP.Net for use with IIS and in most cases fixes the error.
For reference, the full error that I received was as follows:
Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904
Saturday, November 8, 2008
Missing Tabs In Display Properties
Some spyware may create a desktop background to replace your own. After doing this, I’ve seen the display properties tabs for modifying the screensaver and wallpaper disappear to prevent the user from getting rid of the malicious wallpaper.
To bring these tabs back, navigate to the following Registry string:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System
Here, you will find the keys responsible. They are:
NoDispBackgroundPage
NoDispAppearancePage
These will likely be set to 1. Set them to 0 or delete them to get your tabs back.
Registry Editing has been disabled by your administrator
Many people face this error message when they try to open Registry Editor and they have a malware/spyware installed.
Thanks to http://windowsxp.mvps.org/tweakuirest.htm the following gives the solution for the same:
Removing the DisableRegistryTools restriction
For standalone Windows XP systems, perform the steps below to remove the registry editing restrictions.
Method 1: Using the REG.EXE console tool
1. Click Start, Run and type this command:
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0 /f
Please note that the above command is all one line, so please copy the complete command and then run it.
You should be able to launch Tweak UI, as well as the Registry Editor.
Method 2: Using the Group Policy Editor (Windows XP Professional only)
Click Start, Run and type gpedit.msc and press ENTER
Go to the following location:
User Configuration Administrative Templates System
Double-click Disable registry editing tools and set it to Not Configured
Exit the Group Policy Editor
Note: If the setting already reads Not Configured, set it to Enabled, and click Apply. Then revert it back to Not Configured. This ensures that the DisableRegistryTools registry value is removed successfully.
Spanish version of the article is here.
Thanks to http://windowsxp.mvps.org/tweakuirest.htm the following gives the solution for the same:
Removing the DisableRegistryTools restriction
For standalone Windows XP systems, perform the steps below to remove the registry editing restrictions.
Method 1: Using the REG.EXE console tool
1. Click Start, Run and type this command:
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0 /f
Please note that the above command is all one line, so please copy the complete command and then run it.
You should be able to launch Tweak UI, as well as the Registry Editor.
Method 2: Using the Group Policy Editor (Windows XP Professional only)
Click Start, Run and type gpedit.msc and press ENTER
Go to the following location:
User Configuration Administrative Templates System
Double-click Disable registry editing tools and set it to Not Configured
Exit the Group Policy Editor
Note: If the setting already reads Not Configured, set it to Enabled, and click Apply. Then revert it back to Not Configured. This ensures that the DisableRegistryTools registry value is removed successfully.
Spanish version of the article is here.
Saturday, November 1, 2008
MySpace bids for socializing on Google phone
MySpace is the first to unveil an app for owners of the just-released G1 phone powered by Google Inc.'s Android operating system.
News Corp. owned MySpace announced a mobile application for the G1 that can be downloaded wirelessly to the device through the Google-run Android Market. The Market is stocked with add-on programs and games built by third-party developers.
The T-Mobile G1 (made by HTC) costs $179 with a two-year contract in the US.
MySpace's Android application lets G1 users do many of the same things they can do from a desktop computer, like look at profiles and photos on MySpace. In addition, the application lets G1 users quickly upload photos from the phone to their MySpace profiles.
There's no mobile Facebook program for the Android Market yet, but both MySpace and Facebook have already courted iPhone users with programs that let people stay connected.
News Corp. owned MySpace announced a mobile application for the G1 that can be downloaded wirelessly to the device through the Google-run Android Market. The Market is stocked with add-on programs and games built by third-party developers.
The T-Mobile G1 (made by HTC) costs $179 with a two-year contract in the US.
MySpace's Android application lets G1 users do many of the same things they can do from a desktop computer, like look at profiles and photos on MySpace. In addition, the application lets G1 users quickly upload photos from the phone to their MySpace profiles.
There's no mobile Facebook program for the Android Market yet, but both MySpace and Facebook have already courted iPhone users with programs that let people stay connected.
Subscribe to:
Posts (Atom)