This is a common problem faces anyone who installs SQL Server 2005 on windows Vista , S/he tries to login with the admin user on his computer and bang S/he founds that the login fails , S/he checks all the services and found them running ok , so ...

well the solution is simple , all the users in the administrators group on windows vista don't have access on the SQL Server 2005 , you will have to give them access through the SQL Server Surface Area Configuration , you will find a little link says "Add New Administrator" you click on it and add the role you want to what so ever of your users, check below the snapshots from the two windows.

Consider the following support issues when you run the SQL Server "Katmai" June CTP:

• This release is not supported in production environments.
• This release is available in English only.
• This release is available in Developer Edition only.
• Installation must be run from the Servers folder. Tools-only installation is not supported.
• This release is available by download only.
• Upgrade to the SQL Server "Katmai" June CTP from earlier versions of SQL Server is not supported.
• This release has a 180-day trial period. Installations will not function after 180 days.
• Hotfix support is not available for this release.
• Technical support is not available for this release.
• Failover cluster instances are not supported for this release.
• There is no native IA64 support in this release. WOW64 support is for the x64 platform only.

2.3.1 Supportability Known Issues

• Side-by-side tools are not supported. The presence of SQL Server 2005 Management Tools or BI Development Studio blocks installation of SQL Server "Katmai" Management Tools and BI Development Studio. To install the June CTP of SQL Server "Katmai" on a computer where SQL Server 2005 Management Tools or SQL Server 2005 Business Intelligence Development Studio is already installed, use the following syntax at a command prompt:

  Start /wait <CD or DVD Drive>\servers\setup.exe /qb 
  INSTANCENAME=<InstanceName> 
  ADDLOCAL=All REMOVE=Client_Components,SQL_Documentation 
  SAPWD=<StrongPassword> SQLACCOUNT=<domainName\userName> 
  SQLPASSWORD=<domainUserPassword> 
  AGTACCOUNT=<domainName\userName> 
  AGTPASSWORD=<domainUserPassword> 
  ASACCOUNT=<domainName\userName> 
  ASPASSWORD=<domainUserPassword> 
  RSACCOUNT=<domainName\userName> 
  RSPASSWORD=<domainUserPassword> 
  SQLBROWSERACCOUNT=<domainName\userName> 
  SQLBROWSERPASSWORD=<domainUserPassword>

• Side-by-side installation with SQL Server 2000 is not supported. An existing instance of SQL Server 2000, including MSDE, blocks installation of this release of SQL Server "Katmai".
• Side-by-side installation with a default instance of SQL Server 2005 Analysis Services (SSAS) or SQL Server 2005 Reporting Services (SSRS) is not supported. If you install a named instance of the June CTP SSAS or SSRS, installation of a default instance of SQL Server 2005 Analysis Services (SSAS) or SQL Server 2005 Reporting Services (SSRS) fails.
• Side-by-side installation with the March CTP of SQL Server "Katmai" is not supported. An existing instance of the March CTP blocks installation of this release of SQL Server "Katmai".
• Multiple instances of this release of SQL Server "Katmai" are not supported on a single computer.
• The Database Engine Tuning Advisor might not function properly in side-by-side configurations.
  In a side-by-side configuration with a default instance of this release of SQL Server "Katmai" and a named instance of SQL Server 2005, DTAEngine.exe does not correctly load the InstAPI.dll. InstAPI.dll is loaded from the Program Files\Microsoft SQL Server\90\ folder instead of from the Program Files\Microsoft SQL Server\100\ folder.
• By default, Error and Feature Usage Reporting is enabled.
  To disable Error and Feature Usage Reporting after Setup is finished, use the SQL Server Error and Usage Reporting tool on the Configuration Tools menu. To run the reporting tool, click Start, point to All Programs, point to SQL Server 200x, point to Configuration Tools, and then click SQL Server Error and Usage Reporting.
• In SQL Server 2005, SQL Server Browser was an integrated installation together with the Database Engine or SSAS. In SQL Server "Katmai", SQL Server Browser is a separate installation, performed automatically with the Database Engine or SSAS. If you have multiple instances of SQL Server "Katmai", SQL Server Browser will uninstall automatically when the last instance of SQL Server "Katmai" is uninstalled.
  However, if SQL Server 2005 exists on the system with one or more instances of SQL Server "Katmai", SQL Server Browser will not be removed automatically when the last instance of SQL Server "Katmai" is uninstalled. The SQL Server Browser installed with SQL Server "Katmai" will remain on the system to improve connections to the instance of SQL Server 2005. You can leave SQL Server "Katmai" Browser installed with SQL Server 2005 and it will continue to function correctly.
  To uninstall all components of SQL Server "Katmai", you must uninstall SQL Server Browser manually using Add or Remove Programs in Control Panel. If you remove SQL Server Browser when a named instance of SQL Server 2005 is present, connectivity to SQL Server 2005 might become disrupted. If this occurs, you can re-install SQL Server Browser in one of the following ways:
  • Repair the instance of SQL Server 2005 through Add or Remove Programs.
  • Install an instance of the SQL Server 2005 Database Engine or SSAS.
• SQL Server "Katmai" Books Online does not automatically install if SQL Server 2005 Books Online is already installed.
  To install SQL Server "Katmai" Books Online, run SqlServerKatmai_BOL.msi after SQL Server "Katmai" Setup is finished. In the June CTP, this file is located in the \Tools\Setup folder. You can also download this file from the Microsoft Connect Web site June CTP Books Online download page.
• By default, sample code and sample databases are not installed in this release.
  Do not use AdventureWorksDWSamples, SQL_AdventureWorksASSamples, or SQL_AdventureWorksSamples unattended parameters in this release. You can download samples from the Microsoft SQL Server Samples and Community Projects Web site. For more information about samples, see the documentation at Start/All Programs/Microsoft SQL Server "Katmai"/Documentation and Tutorials/Microsoft SQL Server Samples Overview.
• SQL Server Browser and SQLWriter files install to the SQL Server 2005 default directory: <drive>:\Program Files\Microsoft SQL Server\90\Shared\.
• SQL Server 2005 Configuration Manager uses the SQL Server Native Client 9 configuration. SQL Server "Katmai" Configuration Manager uses SQL Server Native Client 10. Both versions can function in a side-by-side configuration.

Updating the Location for the .NET Framework CLR Samples

Before you compile .NET Framework common language runtime (CLR) samples for SQL Server, verify that the path of the version of the .NET Framework compiler is the first Framework directory in the PATH environment variable. The location of the compiler that is shipped with this release of SQL Server is C:\<Windows root directory>\Microsoft.NET\Framework\v2.0.x. Drive C is the installation drive, <Windows root directory> is either Windows or WINNT, and x is five digits.

3.4 Planned Removal of SQLXML

SQLXML is included in this CTP release of SQL Server "Katmai". SQLXML will be removed from the "Katmai" installer in a future CTP release and offered as a separate component instead.

Database Engine

The following issues apply to Database Engine when SQL Server "Katmai" is installed.

4.1.1 Stored Procedure sp_helpuser Fails When Passing Role Name

The following message appears when you supply the role name as a parameter for sp_helpuser:

Msg 15198, Level 16, State 1, Procedure sp_helpuser, Line 166

Do not supply a role name as a parameter for sp_helpuser in the "Katmai" June CTP. This stored procedure is changing and will support passing a role name in a subsequent CTP release.

4.1.2 Language Reference

• MERGE is a fully reserved keyword when the database compatibility level is set to 100. The MERGE statement is also available under both 90 and 100 database compatibility levels, but the keyword is not fully reserved when the database compatibility level is set to 90.
• Full-text predicates are no longer allowed in the OUTPUT clause when the database compatibility level is set to 100.
• The target table of an OUTPUT INTO clause cannot have any enabled triggers defined on it.
• A user-defined function cannot be created if it contains an OUTPUT INTO clause whose target is a table.

4.1.3 Cleanup Tasks Cannot Be Added by Using Maintenance Plan Wizard

In this version of SQL Server "Katmai", the Maintenance Plan Wizard fails if you try to add a cleanup task. To add a cleanup task to a maintenance plan, use the maintenance plan designer instead of the Maintenance Plan Wizard. For example, you can create the basic maintenance plan by using the wizard, and then add a cleanup task by modifying the plan in the designer. To modify the plan using the designer, right-click the plan and then select Modify.

4.1.4 Error When Trying to Connect to a SQL Server Compact Edition version 3.5 Database

In SQL Server Management Studio, you will get an error message when you try to connect to a SQL Server Compact 3.5 version 3.5 database. For example, the message appears when you use the Connect to Server dialog box and select either New database or Browse for More in the Database File drop-down menu.

This error occurs because SQL Server Compact 3.5 3.5 is not yet integrated into the June CTP. Therefore, you cannot connect to SQL Server Compact 3.5 3.5 database. Support for SQL Server Compact 3.5 3.5 will be added in a later CTP release.

4.2 Analysis Services

The following issues apply to Analysis Services when SQL Server "Katmai" is installed.

4.2.1 Clicking the Calculations Tab in Business Intelligence Development Studio Might Generate an Error Message

Double-clicking an Analysis Services project file to open both Business Intelligence Development Studio and the project might generate an error message when you click the Calculations tab. You can receive this error message if the project file is in a different directory from the default directory that Business Intelligence Development Studio uses.

To prevent this error, open Business Intelligence Development Studio, and then open the Analysis Services project from within the studio environment.

4.3 Integration Services

The following issues apply to Integration Services when SQL Server "Katmai" is installed.

4.3.1 Version Change for SQL Server Native Client

SQL Server "Katmai" uses a different version of the SQL Server Native Client from the one included in SQL Server 2005. (SQL Server Native Client was previously known as SQL Native Client.) Therefore, Integration Services packages that use SQL Server Native Client and were created in SQL Server 2005 cannot run automatically in SQL Server "Katmai". To run these packages, follow one of these steps:

• On the computer that is running SQL Server "Katmai", install the version of SQL Server Native Client (sqlncli.dll) that SQL Server 2005 uses.

  Note:

  As of the March CTP of SQL Server "Katmai", you can install the version of SQL Server Native that SQL Server 2005 uses side-by-side with the version that SQL Server "Katmai" uses. However, you cannot install SQL Server 2005 and SQL Server "Katmai" side-by-side.

• Revise the connection strings in the package to specify the version of SQL Server Native Client that SQL Server "Katmai" uses. To revise the connection strings, replace SQLNCLI.1 with SQLNCLI10 or SQLNCLI10.1.

4.3.2 Version Change for Analysis Services OLE DB Provider

SQL Server "Katmai" includes a different version of the Analysis Services OLE DB provider from the one included in SQL Server 2005. Therefore, Integration Services packages that use the Analysis Services OLE DB provider and were created in SQL Server 2005 cannot run automatically in SQL Server "Katmai". To run these packages, follow one of these steps:

• On the computer that is running SQL Server "Katmai", install the Analysis Services 9.0 OLE DB provider. The Analysis Services 9.0 OLE DB provider is the version of the provider that SQL Server 2005 includes.

  Note:

  As of the March CTP of SQL Server "Katmai", you can install the Analysis Services 9.0 OLE DB provider side-by-side with the Analysis Services 10.0 OLE DB provider. (The Analysis Services 10.0 OLE DB provider is the version that SQL Server "Katmai" uses.) However, you cannot install SQL Server 2005 and SQL Server "Katmai" side-by-side.

• Revise the connection strings in the package to specify the Analysis Services 10.0 OLE DB provider. To revise the connection strings, replace MSOLAP.3 with MSOLAP or MSOLAP.4. If you specify MSOLAP, your packages will use the latest installed version of the provider.

4.3.3 Installing SQL Server "Katmai" Removes Support for DTS in SQL Server 2005 Integration Services Packages

For this CTP release, you must uninstall SQL Server 2005 Workstation Components before installing the SQL Server "Katmai" Workstation Components. Uninstalling the SQL Server 2005 Workstation Components removes three Integration Services components: the SQL Server 2005 version of the Execute DTS 2000 Package task and two supporting assemblies. These three Integration Services components support backward compatibility between SQL Server 2005 and SQL Server 2000 Data Transformation Services (DTS). Without these three components, SQL Server 2005 packages and tools that require DTS support will not run.

However, SQL Server "Katmai" Integration Services includes a version of the Execute DTS 2000 task and the two supporting assemblies. Therefore, you can upgrade SQL Server 2005 packages that require DTS support to the SQL Server "Katmai" format by opening them in the SQL Server "Katmai" version of Business Intelligence Development Studio, and then running those packages as SQL Server "Katmai" packages.

4.3.4 Custom Applications That Use Both Integration Services and System.Data.SqlClient APIs Might Fail

A custom application that uses both Integration Services and .NET Framework Data Provider for SQL Server (System.Data.SqlClient) APIs will fail if the following conditions are true:

• The custom application uses the .NET Framework Data Provider for SQL Server APIs before the application uses the Integration Services APIs.
• The custom application runs on a computer that has both SQL Server "Katmai" and an edition of SQL Server 2005 that does not support some or all of the features of Integration Services.

Under these conditions, the custom application incorrectly detects the version of SQL Server as the edition of SQL Server 2005 that does not support Integration Services. This erroneous detection causes the custom application to fail when it calls the Integration Services APIs and to generate a DTS_E_PRODUCTLEVELTOLOW error. This error indicates that Integration Services is not supported on the detected version of SQL Server.

This failure does not occur in the following situations:

• When running packages in the design environment.
• When using dtexec.exe to run packages outside the design environment.
• When the custom application uses Integration Services APIs, but does not use the .NET Framework Data Provider for SQL Server APIs.

4.3.5 Custom Components Developed in SQL Server 2005 Integration Services Must Be Edited and Recompiled for SQL Server "Katmai"

If you developed a SQL Server 2005 Integration Services (SSIS) custom component, that custom component must be modified before it can be used in SQL Server "Katmai" Integration Services packages. You can either modify the component to run only in SQL Server "Katmai" packages or to run in both SQL Server 2005 and SQL Server "Katmai" packages.

Use the Custom Component Only in SQL Server "Katmai" Packages

After completing the following procedure, you can use the component in SQL Server "Katmai" packages, but can no longer use the component in SQL Server 2005 Integration Services (SSIS) packages.

To use a SQL Server 2005 Integration Services custom component only in SQL Server "Katmai" packages

1. In the component, change the references that point to the SQL Server 2005 versions of the Integration Services assemblies to point to the SQL Server "Katmai" versions (version 10.0) instead.
2. Change any code that uses the IDTSxxx90 interfaces to use the corresponding IDTSxxx100 interfaces.
3. Rebuild the component.
4. Reinstall the component in the global assembly cache (GAC).
5. For use in the Toolbox, redeploy the component to the appropriate subfolder under C:\Program Files\Microsoft SQL Server\100\DTS.
6. If you have changed the assembly version of the component, you must also manually edit packages to use the new version.

Use the Custom Component Only in Both SQL Server 2005 and SQL Server "Katmai" Packages

After completing the following procedure, you will have two versions of the custom component: the original version and a SQL Server "Katmai" version. You can still use the original version in SQL Server 2005 packages, but you will have to use the SQL Server "Katmai" version in SQL Server "Katmai" packages.

To create a separate SQL Server "Katmai" version of the custom component

1. Change the file name (assembly name) of the component.
2. In the component, change the references that point to the SQL Server 2005 versions of the Integration Services assemblies to point to the SQL Server "Katmai" versions (version 10.0) instead.
3. Change any code that uses the IDTSxxx90 interfaces to use the corresponding IDTSxxx100 interfaces.
4. Build the component with a new ProgID and CLSID.
5. Install the component in the global assembly cache (GAC).
6. For use in the Toolbox, deploy the component to the appropriate subfolder under C:\Program Files\Microsoft SQL Server\100\DTS.
7. Manually edit packages to use the new version.

4.3.6 Limited Namespaces Included in Books Online

For this CTP release, Books Online includes the documentation for only the following Integration Services namespaces:

• Microsoft.SqlServer.Dts.ManagedMsg
• Microsoft.SqlServer.Dts.Pipeline.Wrapper
• Microsoft.SqlServer.Dts.Runtime.Wrapper
• Microsoft.SqlServer.Dts.Tasks.ExecutePackageTask

For information about additional namespaces, see the SQL Server 2005 Integration Services Class Library on MSDN.

4.4 Reporting Services

The following issues apply to Reporting Services when SQL Server "Katmai" is installed.

4.4.1 Reporting Services in SharePoint Mode

Reporting Services in SharePoint integrated mode is not supported in this CTP release of "Katmai".

4.4.2 Reporting Services New Functionality

This version of SQL Server "Katmai" includes support for features that were released with SQL Server 2005 Service Pack 2: Hyperion Essbase data source support, report model generation from Oracle 9.2.0.3 or later data sources, and the Select All check box for multivalued parameters. These features are fully documented in Books Online.

4.5 All Business Intelligence Technologies

The following issues apply to all of the business intelligence technologies—Analysis Services, Integration Services, and Reporting Services—when SQL Server "Katmai" is installed.

4.5.1 Remove SQL Server 2005 Workstation Components before Installing SQL Server "Katmai"

In the SQL Server "Katmai" version of Business Intelligence Development Studio, the designers that you use to create projects for Integration Services, Analysis Services, and Reporting Services cannot be installed side-by-side with the SQL Server 2005 designers. For both SQL Server "Katmai" and SQL Server 2005, these designers are part of the Workstation Components that SQL Server installs. However, for this CTP release, you cannot install the SQL Server "Katmai" designers if the SQL Server 2005 Workstation Components are already installed on the computer. You must uninstall the SQL Server 2005 Workstation Components before installing SQL Server "Katmai". If you try to install SQL Server "Katmai" without first uninstalling the SQL Server 2005 Workstation Components, you will be notified that the existing components on the computer are blocking the installation. To uninstall the existing Workstation Components, in Control Panel, open Add or Remove Programs, select SQL Server 2005, click Remove, and on the Component Selection page of the wizard, select Workstation Components. Once you have uninstalled the SQL Server 2005 Workstation Components, you can install the SQL Server "Katmai" designers by installing SQL Server "Katmai".

4.5.2 Cannot Edit SQL Server 2005 Business Intelligence Projects in SQL Server "Katmai"

To create projects for Integration Services, Analysis Services, or Reporting Services, you use their respective designers in Business Intelligence Development Studio. However, the designers in SQL Server "Katmai" cannot be installed side-by-side with those from SQL Server 2005. Furthermore, installing SQL Server "Katmai" replaces designers that were installed by SQL Server 2005 with the SQL Server "Katmai" versions.

You can use the SQL Server "Katmai" designers to open and modify projects that were created by using the SQL Server 2005 designers. However, if you use the SQL Server "Katmai" designers to modify SQL Server 2005 Business Intelligence projects, you can no longer save those projects in the SQL Server 2005 format. Upon opening a SQL Server 2005 project, the designer upgrades the project in memory to the SQL Server "Katmai" format. To permanently replace the SQL Server 2005 version of the project with the upgraded SQL Server "Katmai" version, you must either save the upgraded version of the project or perform an operation, such as running an Integration Services package, that will cause the upgraded version of the project to be saved. Otherwise, the upgraded version will not be saved.