Mittwoch, Dezember 02, 2009

Disable the authentication loopback check

Re-enable the behavior that exists in Windows Server 2008 by setting the DisableLoopbackCheck registry entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1.

To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

Note You must restart the server for this change to take effect. By default, loopback check functionality is turned on in Windows Server 2003 SP1, and the DisableLoopbackCheck registry entry is set to 0 (zero).

The security is reduced when you disable the authentication loopback check, and you open the Windows Server 2003 server for man-in-the-middle (MITM) attacks on NTLM. (emphasis mine)

Team Explorer clear local cache

While switching between TFS Server (Team Foundation Server) it often happen that cached data on your local drive mass up connections.

To manage this simply clear the local folder which is used by the Team Explorer as local cache and everything should work again as planned.

What to do:

  • Close your Visual Studio
  • Navigate on your local drive to this location: "%userprofile%\Local Settings\Application Data\Microsoft\Team Foundation\2.0"
  • At this location you find a folder called "Cache" which is used by Team Explorer
  • You simply can rename the folder or even delete it. Team Explorer creates a new one upon next Start-Up of Visual Studio.
  • Start Visual Studio and access your TFS (Team Foundation Server) with a clean Team Explorer cache
enjoy :-)

Note: sometimes this applies if you try to create Team Project and it fails with the errro: TF30177. The above mention steps also helped me to resolve this issue: "TF30177: Team Project Creation Failed -> TFS 2010 Beta 2" - under Windows Server 2008 the cache folder of Team Explorer 2010 is located here: C:\Users\{username}\AppData\Local\Microsoft\Team Foundation\3.0\

Error
Unable to connect to the specified SQL Server Reporting Services at http://
{ServerName}/ReportServer/ReportService2005.asmx.
Explanation
The Project Creation Wizard was not able to connect to the SQL Server Reporting Services at http://{ServerName}/ReportServer/ReportService2005.asmx. The reason for the failed connection cannot be determined at this time. Because the connection failed, the wizard was not able to complete creating the SQL Server Reporting Services site.
User Action
Contact the administrator for the SQL Server Reporting Services at http:///ReportServer/ReportService2005.asmx to confirm that the server is available on the network and you have sufficient privileges to create a project. Also, you might find additional helpful information in the project creation log. The log shows each action taken by the wizard at the time of the failure and may include additional details about the error.


Sonntag, November 29, 2009

hack your own SQL Server 2008 with builtin\adminstrator

in my case we change the sa Pwd and this helped me out to reset:

http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx

Samstag, November 28, 2009

write setup batch file based on processor architecure

take the following lines put it into a *.bat file and based on your OS the correct setup will be started.

@echo off
if /i "%PROCESSOR_ARCHITECTURE%" == "X86" "%~d0%~p0\x86\setup.exe"
if /i not "%PROCESSOR_ARCHITECTURE%" == "X86" "%~d0%~p0\x64\setup.exe"

Freitag, November 27, 2009

TF30335: Connecting a Visual Studio 2008 Client SP1 to TFS 2010 (Team Foundation Server) Beta 2

Some Visual Studio 2008 SP1 installations can have a problem to connect TFS 2010 (Team Foundation Server) beta 2.



Simply add a Registry Key:
- Location: HKEY_CURRENT_USER/Software/Microsoft/VisualStudio/9.0/TeamFoundation/Servers
- String Type
- Value: http://your.tfs-machine.com:8080/tfs/DefaultCollection

Values to replace:
- your.tfs-machine.com: your FQNS (http://www.sharedcache.com)
- DefaultCollection: your collection name

Restart Visual Studio, done!

Shared Cache - .Net Caching made easy

All information about Shared Cache is available here: http://www.sharedcache.com/. Its free and easy to use, we provide all sources at codeplex.