Microsoft .NET Framework 3.5 Readme

          1. System Requirements

• 1.1. Supported Architectures
• 1.2. Supported Operating Systems
• 1.3. Hardware Requirements
• 2. Known Issues
• 2.1. Installing
• 2.2. Uninstalling
• 2.3. Product Issues
• 2.3.1. General Issues
• 2.3.2. Windows Communication Foundation (WCF)
• 2.3.3. Windows Presentation Foundation (WPF)
• 2.3.4. Windows Workflow Foundation (WF)
• 3. Related Links

1. System Requirements

1.1. Supported Architectures

x86

x64

ia64 (Windows Server 2008)

1.2. Supported Operating Systems

Microsoft Windows XP

Microsoft Windows Server 2003

Windows Vista

Windows Server 2008

1.3. Hardware Requirements

Minimum: 400 MHz CPU, 96 MB RAM, 800x600 256-color display

Recommended:  1.0 GHz or higher CPU, 256 MB or more RAM, 1024x768 high-color 32-bit display

Up to 500 MB of hard disk space may be required 

2. Known Issues

2.1. Installing

2.1.1. Uninstall earlier pre-release versions of .NET Framework 3.5 prior to installing the released version.

If you have installed earlier pre-release versions of .NET Framework 3.5, then you must uninstall them prior to running this installation by using Add or Remove Program.

To resolve this issue:

There's no workaround available.

2.1.2. Installing .NET Framework 2.0 or .NET Framework 3.0 stand-alone ENU language package MSU (shipped on media) but the .NET Framework 2.0 or .NET Framework 3.0 language package is already installed.

When one of the following files is being installed, a message, "the following updates were not installed" is displayed.

WCU\dotNetFramework\dotNetMSP\x64\NetFX2.0-KB936704-v6000-x64_RTM_en.msu
WCU\dotNetFramework\dotNetMSP\x64\NetFX3.0-KB936705-v6000-x64_RTM_en.msu
WCU\dotNetFramework\dotNetMSP\x86\NetFX2.0-KB936704-v6000-x86_RTM_en.msu
WCU\dotNetFramework\dotNetMSP\x86\NetFX3.0-KB936705-v6000-x86_RTM_en.msu

This happens because the corresponding .NET Framework 2.0 or .NET Framework 3.0 En-US language package is already installed.

To resolve this issue:

Install .NET Framework 3.5 by using the installation instructions on http://go.microsoft.com/fwlink/?LinkId=96339.

2.1.3. .NET Framework 3.5 does not install on Windows Server 2003 Itanium architectures.

Installing .NET Framework 3.5 on Windows Server 2003 for Itanium 64-bit processors produces the following message: "Microsoft .NET Framework 3.5 - You must first install Microsoft .NET Framework 2.0 SP1 before installing or repairing".

To resolve this issue:

No workaround is available. .NET Framework 3.5 is not supported on Windows 2003 for Itanium 64-bit processors.

2.1.4. .NET Framework 3.5 installation might not configure IIS correctly on Windows XP or Windows Server 2003

Installation of .NET Framework 3.5 will not configure IIS correctly on Windows XP or Windows Server 2003 if IIS is already installed and the IIS Admin Service is disabled.

To resolve this issue:

Do the following things after you install .NET Framework 3.5.

1. On the Start menu, click Run.

2. Type "cmd" and then press ENTER.

3. Type "sc config iisadmin start= auto" and then press ENTER.

-or-

1. On the Start menu, click Run.

2. Type "services.msc" and then press ENTER.

3. Select the IIS Admin Service from the list. If the Startup Type is Disabled, right-click IIS Admin Service and then click Properties. Change Startup Type to Automatic.

4. In %WINDIR%\Microsoft.NET\Framework\v3.5\, run WFServicesReg.exe /c.  (On 64-bit computers, the path is %WINDIR%\Microsoft.NET\Framework64\v3.5\.)

2.1.5. .NET Framework 3.5 reinstallation displays a re-try dialog box.

When customers install .NET Framework 3.5 and then reinstall it, they may see a re-try dialog box that prompts them to close Setup.

To resolve this issue:

Clicking the retry button is harmless. Setup will typically continue because an instance of Setup is already running.

2.1.6. Upgrading .NET Framework 3.5 Beta 1 to the release version might fail on Windows Vista RTM.

User installs .NET Framework 3.5 Beta 1 on Windows Vista and then upgrades to the .NET Framework 3.5 release version.  .NET Framework 2.0 and .NET Framework 3.0 files might not be correctly upgraded if Windows Vista Beta 1 updates are not removed first.

To resolve this issue:

1. If you have already tried to install .NET Framework 3.5, uninstall it.

2. Uninstall the following KBs by using Installed Updates.

- KB929300

- KB930264

- KB110806

3. Install .NET Framework 3.5.

2.1.7. Download of .NET Framework Setup fails.

2.1.7.1. Configuration Errors

This error occurs when BITS interfaces are not registered or the registry settings are corrupted.

To resolve this issue:

- Upgrade to BITS 2.0 from http://www.microsoft.com/downloads/details.aspx?FamilyId=B93356B1-BA43-480F-983D-EB19368F9047&displaylang=en

-or-

- Repair the BITS service by running the Bitsadmin tool at the command prompt, as follows: bitsadmin /util /repairservice /force

You can download the Bitsadmin tool from: http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en.

2.1.7.2. Network Errors

These errors may occur for the following reasons:

- Unable to reach download server.

- URL not found on the server.

- Server is overloaded.

- Bad Gateway or Proxy.

- Network is disconnected.

- Proxy does not support HTTP 1.1.

To resolve this issue:

1. Make sure that you are connected to the network. You may have to exit Setup.

2. Do one of the following things.

- Provide correct settings for the proxy server and ensure that your computer can correctly resolve the proxy server.

-or-

- Upgrade to BITS 2.0. You can download BITS 2.0 from
http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en .

2.1.7.3. Disk Errors

This error occurs when the BITS service failed to create a file or write to a file. Because another program, such as chkdsk.exe, might be running, the disk might be locked and BITS might be prevented from writing to the file.

To resolve this issue:

- Make sure that no other program that could lock the disk is running and then try the download again.

-or-

- Restart the computer and then run Setup again. Make sure that you are connected to the Internet.

2.1.7.4.Proxy Errors

The BITS service failed because of one of the following proxy-related errors:

- The Proxy settings are not valid.

- The proxy server requires authentication.

- The computer is not able to resolve the proxy server.

To resolve this issue:

- Provide correct credentials for proxy server authentication and then start Setup again.

-or-

- Upgrade the proxy server to support HTTP1.1 and ensure that the proxy supports implicit credentials (for example, NTLM). You may have to contact your network administrator.

-or-

Bypass the proxy server by changing your Internet Explorer proxy settings.

To bypass a proxy server:

1. In Internet Explorer, click Tools and then click Internet Options.

2. Click the Connections tab and then click LAN Settings.

3. Under Proxy server, clear Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections.) and then click OK.

4. Click OK again.

If you need further assistance with your proxy server settings, contact your network administrator.

2.1.7.5. Other Errors

The BITS Service does not run in the following scenarios:

- Safe-boot mode.

- On Windows 2000 from a remote desktop connection.

- When Setup is installed by using a "run as" command.

To resolve this issue:

No workaround is available. These scenarios are not supported.

2.1.8. Some components of .NET Framework 3.5 will not be present on the computer after an upgrade to Windows Vista RTM from Windows XP or Windows Server 2003.

Some components of .NET Framework 3.5 will not be present on the computer after an upgrade to Windows Vista RTM from Windows XP or Windows Server 2003.

To resolve this issue:

1. Uninstall .NET Framework 3.5.

2. Reinstall .NET Framework 3.5 from the Visual Studio 2008 DVD or from http://www.microsoft.com.

2.1.9. .NET Framework 2.0 SP1 Setup fails on Windows 2000 SP4 and displays the error message, "The procedure entry point HeapSetInformation could not be located in the dynamic link library KERNEL32.dll."

.NET Framework 2.0 SP1 Setup fails on Windows 2000 SP4 and displays the error message, "The procedure entry point HeapSetInformation could not be located in the dynamic link library KERNEL32.dll."

To resolve this issue:

Install kb835732 from http://go.microsoft.com/fwlink/?LinkID=104408&clcid=0x409.

2.1.10. During .NET Framework installation or uninstalling, a dialog pops up and asks you to close setup process.

During Installation or Uninstalling of .NET Framework 3.5, .NET Framework 3.0 Service Pack 1, and .NET Framework 2.0 Service Pack 1, a dialog pops up with the message "The following application should be closed before continuing with setup:"

The list of applications shown contains the setup itself, and looks like the below:

Microsoft .NET Framework 3.5 Setup

setup

To resolve this issue:

Click on "Ignore" and continue with setup.

2.1.11. "Installer encountered an error: 0x8007177f. This machine is disabled for file encryption".

Users receive an error message when they try to install an update on a Windows Vista computer in a domain. In the error log, the message is either "Error code 6015 for this component" or "Installer encountered an error: 0x8007177f. This machine is disabled for file encryption".

To resolve this issue:

Apply the update, which is available at http://support.microsoft.com/kb/933595.

2.1.12. Installation fails if the Print Spooler Service is not running

The installation of the XPSEPSC component requires that the Print Spooler Service be running in the ‘Started’ state.  If the Print Spooler Service is not running, the XPSEPSC installer will fail. 

To resolve this issue:

Start the Print Spooler service before you install .NET Framework. To do this:

1. Click Start, point to Settings, click Control Panel, and then double-click Administrative Tools.

2. Double-click Services, click to select Services (Local), right-click Print Spooler, and then click Properties.

3. Click Start, and then click OK.

2.2. Uninstalling

2.2.1. Uninstalling the 64-bit .NET Framework 2.0 may break .NET Framework 1.1.

The original release of .NET Framework 1.1 is 32-bit only. In addition, the .NET Framework 1.1 Setup program contains a launch condition that blocks installation on 64-bit operating systems. After the original release, a shim was added to newer 64-bit operating systems that lets users bypass that launch condition and install .NET Framework 1.1. However, because .NET Framework 1.1 was not designed to be installed on 64-bit operating systems and co-exist with newer versions of the .NET Framework that are designed for 64-bit operating systems (such as .NET Framework 2.0), some .NET Framework side-by-side uninstall scenarios do not work correctly.

The following scenario may cause problems on a 64-bit operating system.

1. Install .NET Framework 1.1.

2. Install .NET Framework 2.0.

3. Uninstall .NET Framework 2.0.

When .NET Framework 2.0 is uninstalled in this scenario, some registry entries that .NET Framework 1.1 relies on are removed and .NET Framework 1.1 no longer works correctly. After .NET Framework 2.0 is uninstalled, .NET Framework 1.1 must be repaired to restore the required registry values.

To resolve this issue:

Do the following things.

1. Download the .NET Framework 1.1 setup package (dotnetfx.exe).

2. On the Start menu, click Run, and then type "cmd" and click OK.

3. Run the following command:  <full path to dotnetfx.exe> /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi".

Instructions for repairing .NET Framework 1.1 are contained in %windir%\Microsoft.NET\Framework\v1.1.4322\1033\repairRedist.htm, which can be found on computers that have .NET Framework 1.1.

2.3. Product Issues

2.3.1. General Issues

2.3.1.1. Repairing .NET Framework 3.0 SP1 by using the Support Info dialog box in Add or Remove Programs requires the user to specify the path of the product installation source.

Repairing .NET Framework 3.0 SP1 by using the Support Info dialog box in Add or Remove Programs requires the user to specify the path of the product installation source.

To resolve this issue:

Repair .NET Framework 3.0 SP1 by using the Change option in Add or Remove Programs.

2.3.1.2. Enabling ASMX tracing breaks SqlString serialization.

Enabling ASMX tracing for an ASP.NET Web service that sends or receives a SqlString instance results in an ArgumentOutOfRangeException error at run time.

To resolve this issue:

Disable ASMX tracing for the ASP.NET Web service.

2.3.1.3. The COM registration for System.Management.Instrumentation.dll, which is included with .NET Framework 3.5, is incorrect because it assumes that the version is 2.0.0.0 when it is actually 3.5.0.0.

Windows Management Instrumentation (WMI) clients get a “Provider Load Failure” error when they attempt to use functionality that is implemented in a WMI provider that leverages the WMI Provider Extensions infrastructure. The cause is an improperly-registered dynamic-link library (DLL). During installation of the .NET Framework 3.5, the System.Management.Instrumentation.dll is not correctly registered to enable COM clients to use the classes that it implements.

To resolve this issue:

1. Click Start, and click All Programs.

2. Click Microsoft Visual Studio 2008 and then click Visual Studio Tools.

3. On Windows operating systems earlier than Windows Vista, click Microsoft Visual Studio 2008 Command Prompt to open a Command Prompt window. On Windows Vista and later operating systems, right-click Microsoft Visual Studio 2008 Command Prompt and then click Run as Administrator to open an elevated Command Prompt window.

4. At the command prompt, type "regasm %systemdrive%\program files\reference assemblies\microsoft\framework\v3.5\system.management.instrumentation.dll" and then press ENTER.

Note: Developers who are writing WMI providers that leverage the WMI Provider Extensions technology (included in .NET Framework 3.5) must ensure that System.Management.Instrumentation.dll is registered properly, and fix the registration if necessary, before they install their providers. Incorrect registration will result in provider failure. The procedure at http://go.microsoft.com/fwlink/?LinkID=103794 shows how to register this DLL correctly.

2.3.1.4. In ASP.NET, LinqDataSource throws System.Security.SecurityException at run time.

As part of the .NET Framework 3.5 Setup, some permissions are added to the default configuration files, web_mediumtrust.config and web_hightrust.config.  These updates are required so that LinqDataSource can be used in medium trust and high trust settings.

Custom trust configuration files cannot be detected by the installer and must be updated manually. If trust settings are not updated, the LinqDataSource control may raise the following runtime exception: "System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.ReflectionPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed."

To resolve this issue:

1. Open the trust configuration file that would typically be installed in the following location: %WINDIR%\Microsoft.NET\Framework\v2.0.50727\CONFIG\.

2. Make the following two changes in this file:

- Under the <SecurityClasses> element, add a nested entry for a new Security Class, as follows:

                    <SecurityClasses>

                               ....

                                                <!-- this SecurityClass section is the work around for the compilation issue -->

                                                <SecurityClass

                                                                Name="ReflectionPermission"

                                                                Description="System.Security.Permissions.ReflectionPermission,

                                                                mscorlib,

                                                                Version=2.0.0.0, Culture=neutral,

                                                                PublicKeyToken=b77a5c561934e089"

                                />

                    </SecurityClasses>

                                               

- In the <NamedPermissionSets> section, nested in the ASP.NET <PermissionSet>, add a <IPermission> element for reflection permission, as follows:

                  <NamedPermissionSets>

                    

                           <PermissionSet

                                  class="NamedPermissionSet"

                                  version="1"

                                 Name="ASP.NET">

                                 ...

                  <!-- this IPermission section is the work around for the reflection issue -->

   <IPermission
                            class="ReflectionPermission"
                                      version="1"
                                      Flags="RestrictedMemberAccess"
                    />

  </PermissionSet>

  ...

  </NamedPermission>

3. Save the file and close it.

2.3.1.5. On Windows XP, existing managed control URL actions for current user are overwritten when user upgrades to .NET Framework 2.0, .NET Framework 3.0, or .NET Framework 3.5.

When the runtime is upgraded from .NET Framework 2.0 or .NET Framework 3.0 to .NET Framework 3.5, any of the existing managed code URL actions for the current user are overwritten by the default settings. For example, URL actions that the user set to "Disabled" could be reset to the default "Enabled". 

The following two URL actions are known to be affected: “Run components not signed with Authenticode” and “Run components signed with Authenticode”.

This behavior occurs on Windows XP, but does not occur on Windows 2003 and Windows Vista.

This behavior also occurs when .NET Framework 1.1 is upgraded to .NET Framework 2.0.

To resolve this issue:

The user must reset URL actions manually after a .NET Framework upgrade.

2.3.1.6. Internet Explorer Setup resets the URL action "Permissions for Components with Manifests" from "Disabled" to "High Safety" during installation.

When Internet Explorer 6 is upgraded to Internet Explorer 7, if the URL action "Permissions for Components with Manifests" is set to "Disabled", it is changed to "High Safety" (the default). This occurs because Internet Explorer 7 Setup does not know that the URL action has been changed from the default; therefore, it resets it to the default. This is noteworthy because the default Medium-High security setting may be less restrictive than the user's previously chosen setting.

To resolve this issue:

The user must reset URL actions manually after an upgrade.

2.3.2. Windows Communication Foundation (WCF)

2.3.2.1. wsHttpBinding that has message security sign-only contract requirements produces non-compliant messages.

WCF emits a <sp:EncryptSignature> assertion in the service’s security policy every time the message security is used in the wsHttpBinding binding. To make WCF compliant with the security policy specification, it does not emit the <sp:EncryptSignature> assertion if the entire service contract is marked as ProtectionLevel.Sign or ProtectionLevel.None and nothing is encrypted in any contract’s operation message (for example, username token).

To resolve this issue:

No workaround is available.

2.3.2.2. Cannot resolve relative externalMetadataLocations when HTTPS and configured MEX endpoints are used. 

When metadata publishing for a WCF service over HTTPS is configured by using ServiceMetadataBehavior with a relative ExternalMetadataLocation, metadata requests cannot be resolved and the following exception message is displayed if any metadata exchange (MEX) endpoints are configured: "The URL supplied to ServiceMetadataBehavior via the ExternalMetadataLocation property or the externalMetadataLocation attribute in the serviceMetadata section in config was a relative URL and there is no base address with which to resolve it."

To resolve this issue:

Remove any configured MEX endpoints from the WCF service.

2.3.2.3. Behavior change: SSL certificates validation and certificate paths.

In earlier releases, if IIS or any other Web server was configured to use HTTPS and to exchange the whole server certificate path instead of just the server certificate, a WCF client might not have accepted the server's certificate as valid when intermediate CA certificate(s) did not exist in the local certificate store. In .NET Framework version 3.5, WCF now handles the certificate paths for server certicate verification.

To resolve this issue:

No workaround is required.

2.3.3. Windows Presentation Foundation (WPF)

There are no known issues.

2.3.4. Windows Workflow Foundation (WF)

2.3.4.1. Workflow Foundation rules cannot use non-public extension methods.

Non-public extension methods that are defined in a workflow project cannot be used as part of Workflow Foundation rules.

To resolve this issue:

Make the extension methods public.

How to Install SQL Server 2008 - A Step by Step Guide

How to Install SQL Server 2008 - A Step by Step Guide

A Step by Step guide to installing SQL Server 2008 simply and successfully with no prior knowledgeDevelopers and system administrators will find this installation guide useful, as will seasoned DBAs. It will teach you the basics required for a typical, problem-free installation of SQL Server 2008, allowing you to add other components later if you wish. Remember to install the .Net Framework 3.5Before you start the installation, you’ll need to install the .Net 3.5 Framework. This comes pre-installed on Windows 2008 Server, but for earlier versions of Windows, you’ll need to install it first. This is a straightforward pre-requisite and is usually included as part of the SQL Server 2008 installation. However, if you don’t know how to do this, or for some reason you need to download it, check out the guide Installing .Net Framework 3.5 for SQL Server 2008. Once this Framework in installed you can commence the installation of SQL Server 2008. STEP 1 : Copy the installation filesFirst off I’d recommend you copy the entire directory structure from the SQL Server 2008 installation disc to the C: drive of the machine you are going to install it on. Although this means you need to grab a cup of coffee whilst it’s copying, this has three advantages: It makes the installation process much faster than running it from CD/DVD once it gets started. It allows you to easily add or remove components later, without having to hunt around for the CD/DVD. If your media is damaged and a file won’t copy, you get to find out now, rather than halfway through the installation. Here’s what my system looks like after the copy: STEP 2 : Setup.exeDouble click on the setup.exe file. After a few seconds a dialog box appears: This will disappear from the screen and then the main installation page appears: STEP 3 : SQL Server Installation Center Click on the Installation hyperlink on the left hand side of the screen: STEP 4 : SQL Server Installation CenterClick on the "New Server stand-alone installation" link on the right side of the screen: The following dialog appears on the screen whilst the install program prepares for installation: After a minute or so (the timing will vary according to your system), the following screen appears: STEP 5 (optional) : If any checks have failed, click on the Show details button or "View detailed report link" to find out the cause, correct it, then click on the Re-run button to perform the checks again. STEP 6 : Product key If all checks have passed, click on the OK button. After a few moments, the option to select the edition and to enter the license key (or “product key”) will appear. Note that the product key box may already be populated, depending on which edition you have. Don’t enter the product key we’ve shown here, it won’t work on your system!: STEP 7 : License TermsEnter the product key into the box, or choose the free edition if you're evaluating SQL Server 2008, and click on the Next button: Click in the "I accept the license terms" check box, then click on the Next button again. STEP 8 : Setup Support Files The following screen appears; click on the Install button: The following screen will appear whilst Windows Installer prepares itself for the installation. This will take a short while: After 30 seconds or so the dialog appears again: STEP 9 : Setup Support Rules If all is well, the following screen appears: Click on the Next button again. STEP 10 : Feature Selection Select the features you want to install. At a minimum, the following are useful (I'd argue essential), but what you need will depend on your needs: Click on the Next button. STEP 11 : Instance Configuration After a short while the following screen appears: For most installations, keep the default settings. Click on the Next button. STEP 12 : Disk Space Requirements This screen just tells you if you have sufficient disk space on the drive you’re installing to, and what’s going to be installed where. Click on Next.

STEP 13 : Server Configuration
This step allows you to set up the service accounts that will be used to run SQL Server. If you have created Windows NT or Active Directory accounts for use with services, use these.If not, then just to get the installation up and working, use the built-in Network Service account for all three services listed (this account does not require a password).
This allows SQL Server to start up after installation. However, it can be easily changed later to another account through the Services applet (Control Panel -> Administrator Tools -> Services):
In addition, remember to change the Startup Type to Automatic, for all three services. This automatically starts the SQL Server database engine, SQL Agent and SQL Browser services when the server is re-booted.The first service runs the SQL Server database engines executable process. The other two services allow scheduled jobs to run after installation (and after a re-boot), and allow the SQL Server to be found by clients on the network.
Do not worry about changing the collation tab, unless there is a specific requirement for anything other than the default collation sequence. Finally, click on Next.

STEP 14 : Database Engine Configuration – Account Provision
This screen allows you to set up database engine security.
Change the Authentication Mode to Mixed Mode unless you are certain you only need Windows-only authentication.

• Many third party applications rely on SQL Server logins to operate correctly, so if you are setting up a server for a third party application, rather than one developed in-house, enabling Mixed Mode authentication is a good idea.

If you pick Mixed Mode security, you must also enter a password for the sysadmin account (sa).Enter and confirm a secure password for the sa account and keep it somewhere safe. Do not give it to any one you do not want to have access to the SQL Server.
Note that you MUST also provide a Windows NT account on the local machine as a SQL Server administrator. If you do not want Windows system administrators to be able walk up to the box and login to SQL Server, create a new, local, dummy Windows user and add this account instead. Otherwise, add in the local administrator account, or your own Windows account on the domain in which the SQL Server will reside.

STEP 15 : Database Engine Configuration – Data Directories
Click on the Data Directories tab.
Change the directories to specify which drives in your system will be used for the various types of database files.Generally it’s advisable to put the User database directory and User log directory on separate physical drives for performance, but it will depend on how Windows has been configured and how many disk drives you have available.
If you are installing on a single drive laptop or desktop, then simply specify:

Data root directory	C:\Program Files\Microsoft SQL Server
User database directory	C:\Data
User log directory	C:\Logs
Temp DB directory	C:\TempDB
Temp Log directory	C:\TempDB
Backup directory	C:\Backups

Do not click on the FILESTREAM tab unless you know you need to change these options, as it is not generally required for most installations, but can easily be changed by using sp_configure 'filestream_access_level', ''after SQL Server has been installed. Click on Next.

STEP 16 : Error Usage ReportingThis screen simply asks if you want to send error information to Microsoft and can safely be skipped if you do not want to share any information.

Click boxes if you want to help Microsoft help you.
Click on Next again…

STEP 16 : Installation Rules
This screen simply checks if there are any processes or other installations running which will stop the installation of SQL Server 2008.
Click on Next again – you’re almost ready to install:

STEP 17 : Ready to InstallThis screen summarises what you are about to install and gives you a last chance to cancel or change anything that’s wrongly configured:
Check that what’s being installed is what you want and then click on Install when you’re sure you want to start the installation process:
Installation ProgressSQL Server 2008 will now install. How long it takes depends on the speed of your machine, what load it’s under, the installation media (CD is slower) and what you’ve chosen to install.
…More Installation Progress

... and Finally
Finally, the installation will complete:
...and the following dialog box will appear:
Click on OK, the machine will NOT reboot.
The following will appear:
…followed by:
Click on the Next button again...STEP 18 : Installation Complete
The following screen appears:
It may be worth clicking on the installation log at the top of the screen to check everything’s gone as expected. Not that this is MUCH smaller than the usual SQL Server installation log files of old.Finally, click on the Close button. The following dialog will appear:
Click on OK – your server will NOT re-boot at this point.
The dialog box will disappear and you will be returned to the Installation Center:
Click on the Close button (the “x”) in the top right of the screen.
Finally, manually reboot your machine to complete the SQL Server 2008 installation.Top Tips :
How to check that SQL Server 2008 has installed correctlyHere are a short number of post-installation checks which are useful to perform after re-booting your new SQL Server. You don’t have to run these, and there are other ways to check, but they are very useful for non-DBAs to be sure that the installation is basically sound and a connection can be made to the new SQL Server before handing it over to someone else.
Check 1: Has the SQL Server Service Started?Check SQL Server 2008 has started.
Check 2: Does Management Studio Work?
Check Management Studio works by firing it up.
Click on NO when you see this dialog box:

Check 3: Can you run a basic query against the new SQL Server?Check SQL Server works by running a simple query from Management Studio:
Enter the query shown below and hit F5 to run it:
Check 4: Is SQL Server Agent Running?
Check SQL Server Agent is running for scheduled jobs. There should be a green arrow next to the SQL Server Agent database symbol (it’s small, you might have to look hard):
Check 5: Can SQL Server be seen from the Network?Check that the new SQL Server can be seen from another SQL Server on the same domain by running isql –L (or osql –L):
If you can’t see the new SQL Server in this list, check that the SQL Server Browser service is started on the machine where you have just installed SQL Server.Check 6: Has the TCP/IP network protocol library been enabled on the server?
If the browser service is started but you still cannot connect to the server, click on Start ->Programs -> SQL Server 2008 -> SQL Server Configuration Manager (on the server where SQL Server’s just been installed)
The SQL Server Configuration Manager window opens.
Click on the SQL Server Network Configuration node and expand it.In the example below, we have MSSQLSERVER (a base instance of SQL Server), and SQLEXPRESS showing as installed.
If in doubt, click on Protocols for MSSQLSERVER.
In the above screenshot, the TCP/IP network protocol library is disabled. We need to enable it in order that remote servers can talk to the newly installed SQL Server.

• A word of explanation : In most installations, Named Pipes can be ignored, unless there is a requirement for it. In virtually all environments, VIA can also be ignored as this protocol requires a special network card. Shared memory is the “local” protocol that SQL Server uses when talking to a client application on the same server as itself, for example when SQL Server Management Studio connects to it. It is usually best to leave this enabled.

You will need the TCP/IP protocol enabled if you need to connect to your new SQL Server from a remote client or another server via TCP/IP, which is what most networks use.
If it shows as DISABLED (above), double click on the TCP/IP protocol line, and the following window will appear:
Ensure that Enabled is set to Yes, and click on OK.
The following warning will appear:
Click on OK, and you will be returned to the Configuration Manager window, where TCP/IP will now be shown as enabled:
Go back to the Services applet, and re-start the MSSQLSERVER service so that the TCP/IP protocol can be used to connect to your new SQL Server.Then try to connect to it again from a remote machine.
If you have experienced problems with the previous connectivity tests, you should now be able to repeat at least some of them successfully.

Mohd. Moheet Nawaz Khan

Social coding -- the next wave in development

Takeaway: New social coding tools are enabling a revolution in product development. Rick Freedman reveals what he sees as the key stumbling block for social development.

In my last post, I pondered some of the new roles that project managers (PMs) will take on as projects become more distributed, dispersed, and diverse. I’m fascinated by the idea of “social coding,” software development by a distributed, virtual community. I decided to do a little research on the tools and technologies that are enabling this new way of thinking about product development.

I’ve seen development environments that contain most of the components of a social coding platform, such as code repositories, wikis, tracking tools, personal profiles, RSS feeds, project microsites, and discussion threads, but they’re frequently rigged together from disparate, incompatible parts. Application lifecycle management environments, which previously were focused on version control, now offer all of these social elements in a single, integrated hub or platform. These capabilities combine to enable a social community that can self-direct and deliver robust products, as open source environments like GitHub have proven.

GitHub claims to be the largest code host in the world, with two million repositories and one million users. According to GitHub’s mission statement,

Code is about the people writing it. We focus on lowering the barriers of collaboration by building powerful features into our products that make it easier to contribute. The tools we create help individuals and companies, public and private, to write better code, faster.

GitHub’s CEO and founder Tom Preston-Werner, said recently:

We like the ideas of social networking. We think that developers work more effectively when they work together. So let’s take the ideas of a social network and add on top of that code hosting, and let’s create a site that makes it easy to share and collaborate on code. We have a way to follow users, and we have a way to watch repositories. In your dashboard you can then see lists of all the people that you’re watching and the actions that they’re doing. If they make commits, if they edit a wiki, whatever they’re doing you can see that. You can get an RSS feed of that. You can see it in a bunch of different ways. It just allows you to keep tabs on what you find important in that eco-system.

We also have the notion of profiles. So you can go to someone’s profile page and see a list of their repositories, when they’ve been working on them, so you can keep tabs on who’s working on what, and to what degree, and if they’re responsible for a project. It makes it easy to see who’s responsible for code in certain places.

The capabilities that we’re accustomed to from social networks like Facebook, and those we often jury-rig together, like tracking and wikis, are now stacked on top of a robust, replicable code repository, to create an environment focused on development communities. Projects become virtual villages, with self-directed development occurring worldwide, and team structures emerging rather than being planned.

Many enterprises shy away from public access repositories for security and control purposes. Products like CollabNet’s TeamForge and other Application Lifecycle Management tools target this enterprise space. CollabNet recently released a new version, 6.1, of TeamForge that specifically touts the company’s “Be Social” philosophy. I chatted with Lothar Schubert, CollabNet’s senior director of product marketing for TeamForge, about the social elements of the product. He said:

The idea of communities is based on the strong heritage of CollabNet in the open source community. Software development happens within the context of a team. The team must interact constantly not only with each other but with the code. Social coding requires the ability to provide collaborative authoring, using tools like wikis that are tied to specific artifacts, to the code. You need collaborative networking capabilities, such as discussion forums and RSS feeds. We also provide the capability to create social networks around shared communities, to build project microsites. Of course, last but not least is the repository of code.

The social coding concepts that have been evolving in the open source community, and are now being integrated into the open source hubs like SourceForge and GitHub, are migrating to the enterprise market, as companies recognize that even their internal projects can be managed as self-directed open source efforts.

I also chatted about social coding and the new tools that enable it with Dave West, a Principal Analyst focused on Application Delivery Professionals for Forrester Research. When we discussed social coding, Dave commented:

We’re social animals, and the development of stuff tends to be social in nature. We think a better way of thinking about it is as social development. It’s not just about the coding; it’s about enabling business change and delivering business value in a social way. It will be interesting to see how CollabNet, with tools like TeamForge, broadens the idea from social coding to social development. Social coding is a fundamental change.

I asked Dave about the challenges of adopting these ideas:

We’re seeing huge productivity gains from developers and testers. We’re now building the wrong software really well. How do we get teams to align to the business, how do we enable a culture of business agility across the enterprise? That’s the tricky stuff, as most companies are built around the factory, hierarchical model, not the collaborative model.

Dave picks out the key stumbling block for social development. Every migration, as from ad hoc to PMI and CMM methods, and from PMI to agile and scrum, gets stuck on the human elements of resistance, agenda and, culture. These new social coding tools enable a revolution in product development through communities; the challenge is getting the organization and the project teams to think and act as communities.

Really It's Matter of concern, if this shit happens then our cars will be at risk!!!

'War texting' lets hackers unlock car doors via SMS

By Robert McMillan

July 27, 2011 01:43 PM ET

2 Comments

 

IDG News Service - Software that lets drivers unlock car doors and even start their vehicles using a mobile phone could let car thieves do the very same things, according to computer security researchers at iSec Partners.

Don Bailey and fellow iSec researcher Mathew Solnik say they've figured out the protocols that some of these software makers use to remote control the cars, and they've produced a video showing how they can unlock a car and turn the engine on via a laptop. According to Bailey, it took them about two hours to figure out how to intercept wireless messages between the car and the network and then recreate them from his laptop.

Bailey will discuss the research at next week's Black Hat conference in Las Vegas, but he isn't going to name the products they've hacked -- they've looked at two so far -- or provide full technical details of their work until the software makers can patch them.

Probably the best known of this type of product is the OnStar RemoteLink app, which can be used to start up and unlock many late-model General Motors vehicles, but similar software is available for other makes of cars, including Mercedes and BMW.

Bailey calls his technique "war texting," a reference to another hacking technique called "war driving," which involves driving around cities looking for data on wireless networks.

War texting is technically complex. First of all, the researchers have to identify cars that are using these mobile applications. Then they have to find a way to connect with them. With these mobile car apps, the phone connects to a server that then sends secret numerical keys to the car in order to authenticate itself, but the iSec researchers figured out ways to get around this by looking at the messages sent between the server and the car over the mobile network, Bailey said in an interview. "We reverse-engineer the protocol and then we build our own tools to use that protocol to contact that system," he said.

The iSec researchers believe that they are uncovering symptoms of a much more widespread problem. In recent years, mobile networking has been built into an astonishing range of devices -- everything from picture frames to cars to smart meters -- giving them a cheap and easy way to communicate. According to Bailey, however, security has often been an afterthought, and many of these products can be hacked and misused.

Research in this area has taken off in recent years as open-source tools have given hackers an inexpensive way of setting up their own mobile-phone test networks.

In April, Bailey used similar techniques to hack Zoombak's personal locator devices, and there are hundreds of other similar products that have not been examined. "This architectural flaw expands to so many engineering industries," he said.

Robert McMillan covers computer security and general technology breaking news for The IDG News Service. Follow Robert on Twitter at @bobmcmillan. Robert's e-mail address is robert_mcmillan@idg.com