Hello, I am deploying SSRS 2005 on Windows Vista and was wondering if there was a way to automate the following three tasks so that my end-users would not have to do them?
Add a URL to the Trusted Sites for the current computer name?
Change the Security Level setting for User Authentication for the Trusted Site added in step #1 to be automatic logon with current username and password?
Change the properties on IE7 to run with Administrative privileges?
I think, but am not sure that some of these can be done with VBScript? If these can't be automated, then end-users of my application will have to go through these 3 steps manually in order to view the SSRS reports that I have written without being prompted to log in, or encountering error messaged due to insufficient privileges.
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
I have a problem when i start sincronyzing with the emulator of MSVS2005 to SQL2005 in Windows Vista. I have the same program in the emulator, but sincronyzing with windows XP Pro and no problem...
"Failure to connect to SQLServer with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the SQL Server, or the password is incorrect"
I'm trying to use SQL Management Studio to connect from a Vista SQL 2005 client w/ SP2 over to a Windows XP workstation running SQL server developer edition (non-sp2) using windows authentication.
I'm already preauthenticated by network shares to the xp workstation. This worked just fine in windows xp but stop working in vista.
After searching around, i found out that vista handles trusted authentication differently than windows xp due to changes in the SSPI. Logging in as sql authentication works fine. Logging in as windows authentication does not.
UPDATE: I found out that two workstations running vista and sql 2005 sp2 cannot connect to each other using windows trusted authentication!!!
What the heck?
UPDATE: I found out that my IIS 7.0 using ASP.NET and connecting to SQL 2005 (non sp2) on a Windows 2003 server (SP1) WILL connect to the database using trusted authentication... apparently IIS can access the credentials and pass them to the sql 2005 box just fine. My Sql 2K5 SP2 tools cannot. I'm forced to use SQL authentication to the box.
Same thing applies with a Windows XP SP2 box running SQL 2005 (non sp2).
Here is my sql server error log off of the windows xp workstation:
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2. 2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100] 2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1. 2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
How can i Fix this issue?
[1] Client side:
What is the connection string in you app or DSN? N/A If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine? Remote
Can you ping your server? YES
Can you telnet to your SQL Server? YES
What is your client database provider? SQL Management Studio
Is your client computer in the same domain as the Server computer? WorkGroup
What protocol the client enabled? Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string? NO
Do you select force encryption on server and/or client? NO
[2] Server side:
What is the MS SQL version? SQL Server 2005
What is the SKU of MS SQL? Developer
What is the SQL Server Protocol enabled? Shared Memory & TCPIP
Does the server start successfully? YES
If SQL Server is a named instance, is the SQL browser enabled? N/A
What is the account that the SQL Server is running under? Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? YES
Do you make firewall exception for SQL Browser UDP port 1434? N/A
[3] Platform:
What is the OS version? Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed? None
[4] Misc:
If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question. N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2. 2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100] 2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1. 2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
[1] Client side:
What is the connection string in you app or DSN? N/A If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine? Remote
Can you ping your server? YES
Can you telnet to your SQL Server? YES
What is your client database provider? SQL Management Studio
Is your client computer in the same domain as the Server computer? WorkGroup
What protocol the client enabled? Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string? NO
Do you select force encryption on server and/or client? NO
[2] Server side:
What is the MS SQL version? SQL Server 2005
What is the SKU of MS SQL? Developer
What is the SQL Server Protocol enabled? Shared Memory & TCPIP
Does the server start successfully? YES
If SQL Server is a named instance, is the SQL browser enabled? N/A
What is the account that the SQL Server is running under? Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? YES
Do you make firewall exception for SQL Browser UDP port 1434? N/A
[3] Platform:
What is the OS version? Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed? None
[4] Misc:
If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question. N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2. 2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100] 2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1. 2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
I want to choose between Windows Vista editions. Please help me I should go for Windows Vista Business or Windows Vista Home Premium as I intend to install SQL Server 2005.
I just installed SQL Server 2005 on Windows Vista Basic platform with just windows authentication, installation went pretty well, but when I tried to logon to the server, it gave me error "Logon failed with error code 18456".
I logged on as administrator, service for SQL server is started, but I can't logon. Can you please help.
I'm currently running Windows Vista x64 and SQL server 2005 on an HP laptop with a AMD Turion 64 processor. I've install all of the Windows Vista x64 update so far with no issues. However, I'm unable to install SQL server 2005 SP2 via Windows updates.
I was able to successfully download the service pack with no issues and it is currenly on my machine ready to install. The system does take a check prior to the install process beginning to perform the install.
I continuely get and "Error Code A91" when the install process is running. As a result the install does not complete successfully. When I used the "Get Help" option I get a list of possible error conditions but none of them seem be useful. I checked each one and none of them provide any help with a solution.
I've successful installed SP2 on Vista x32 system with no problem. Is this a "Windows Update" issue?
I've tried to install all features in the SQL Server 2005 to run on Windows Vista. The Reporting Services failed to install. I think it is because of the IIS 7.0 that 's not recognised by SQL Server.
Is there anyone who have had the same problem and is there anyone who have a suggestion to solve this problem?
Hi, Trying to install SQL Server 2005 on Windows VISTA Ultimate, received following error:
- SQL Server Edition Operating System Compatibility (Warning)
Messages
SQL Server Edition Operating System Compatibility
Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
I have a problem using Remote Data Access (RDA) to connect SQL Server Mobile 3.0 and SQL Server Express 2005 in windows Vista. The problem is that I can't install SQL Server Windows Moble 3.0 because i get a message that no replication componets have been istalled. I thought that installing SQL Server Mobile would do that. Any ideas?
There are numerous posts regarding this error when installing SQL Server 2005 on Windows Vista RTM thus I am starting a new thread in order to get resolution one way or another:SQL Server Setup failed to execute a command for server configuration. The error was [SQL Native Client]Windows user or group "USERNAMESQLServer2005MSFTEUser$USERNAME$MSSQLSERVER" not found. Check the name again... The error occurs when installing SQL Server 2005 Developer Edition, SQL Server Express SP1, SQL Server Express SP2 CTR (with or without the SP2 Toolkit package installed beforehand). The error occurs with or without UAC.
The installation then fails. Please advise if you have any insights. SQL Server Express SP2 CTR was announced as a workable version for Vista... note that this is not the case.
As the titel suggests I am having quite a strange problem
I have installed an Enotebook on our domain server at work and it uses MSQL express 2005. When I ask it to automatically connect using window authentication to connect it works on windows XP machines with DomainUSERNAME. However when I try the same thing on Windows vista it tells me the logon failed with "DomainUSERNAM". I change it to SQL Authetifcation and type the same username fully (I have added the user via active directory as a SQL user) then it works
Basically it looks like the windows username is sent from Vista missing the last letter.
I have Googled this a lot and have not really found an answer. Am I mearly being very stupid or is this a known issue. Can anyone give me a suggestion as to why this might happen?.
I am trying to install SQL Server 2005 on Windows Vista Home Premium edition, when I run the Installer I received are the following error message.
IIS Feature Requirement (Warning)
Messages
IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
I already configure IIS7 with all feature, but system still generate above mentioned message.
have removed bsn contact manager and all sql related files from previous installation attempts, rebooted so should be a clean install - but still it fails
what did I miss or what am I doing wrong?
here are the logs with ref to the two items that fail
~~~
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Professional (Build 6000) Time : Tue Mar 20 18:30:20 2007
Product : OWC11 Error : Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM. --------------------------------------------------------------------------------
Product : Microsoft Office 2003 Web Components Product Version : 11.0.8003.0 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_PATRICES-XPS_OWC11_1.log Last Action : InstallExecute Error String : Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM. Error Number : 1706
thanks for any help/light/suggestions you can share
I tried to install SQL SERVER 2005 through SQLEVAL64 (IA64) on Window vista 2007, Intel core 2 duo processor. Like many other software (including my lexmark printer driver), SQL SERVER 2005 does not seem to be working. Anyone has any work around solution or had similar experience ?
I am having this problem since I installed the new windows Vista.
I am trying to install the SQL Server 2005 developer edition on Windows Vista, but After installation finish successfuly I open the start menu to surprise that I could not find the Shortcuts to open the SQL Server and create new database and tables etc... I opened the full path of the exe files "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE" but there are not any file there, even that I searched for the exe files names but they are not existed. It looks that after instalation complete that the SQL Server is not installed on Windows Vista.
So, my question is: After installing the SQL Server 2005 SP2 for windows Vista, will the problem be solved? Or there is something else to do ON WINDOWS VISTA.
Please, I need the answer for this problem, because I need to work on SQL Server 2005 very hard.
Firstly, can someone confirm that this can be done. Because I am starting to wonder.
I have downloaded the SQL Server 2005 Express install, and attempted to install. Everything goes well. Computer scan indicates that everything is in place, but then when it goes to install the components it states that the following components failed:
(Successful items were SQL Setup Support Files, SQL VSS Writer, OWC11, SQL Server Backward-Compatibility Files, SQL Server Management Studio Express).
For those Items that failed, I just get a message stating "Setup failed. Refer to Setup Log'. The setup log tells me little to nothing about why these components failed.
I am also getting the following message part way through install "An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.mis'". Does anyone know what this means? I downloaded the install from microsoft.com just a few days ago, so if this isn't "valid", then where do I get a valid one.
I'm totally stuck. Have spent almost a day trawling documentation etc. to find why these have not installed, but cannot find any indication of why they wont install.. everything that needs to be in place is. Hoping someone has had similar issues and can help.
I want to create deployment for MS SQL 2005 Express database, that creates database, tables and inserts data. I have made a similar with VisualStudio 2003 and MSDN
I have just take my system back to the factory defaults after some unsuccessful attempts to install 64 bit and 32 bit sql server on my notebook. I am looking to use either 32 or 64 bit (I have disks for both) and I would like to get a step by step guide that will help me through the process.
I tried an install of the 64 bit version, applied SP2, and it went smoothly but the report services browser didn't work. I tried to change some IIS settings but I didnt document what I changed so i was unable to undo the changes that i made when these didnt work.
I tried several combinations of things but then decided that a clean install on a clean system was the best option.
I need the SQL engine , reporting services, analysis services - and possibly integration services - i am not sure if i need notification services (dont know what it does anyway!)
I also have vs2005 - should i install that first or after sql server 2005 SP2?
I have a problem when i want to debug an ssis component under visual studio 2005.
I'm using sql 2005 with service pack 2 and i have already install patch for visual studio under vista.
When i put a breakpoint for exemple in the method "public override void PreExecute()" or in the other method. "public override void ProcessInput(int inputID, PipelineBuffer buffer)" and i execute the pgm.
however when i begin debugging,it's always skip breakpoint
However when i put a break point in the Validate method "public override DTSValidationStatus Validate()" it function.
Unit tests in our project make use of cp utility to import data into database. But the performance of running unit tests under XP and Vista differs much. The difference that I was able to notice is in CPU percentage usage: approximately 5% (XP) against 10% (Vista).
What can be the reason for bcp run slower under Vista?
First, I am a consultant and have several clients. Before upgrading to Vista, I used Windows XP and was able to use SQL Server Management Studio to connect to SQL Servers (2000 and 2005) using my saved network passwords. I would establish a connection to the remote SQL Server by doing a Start - Run "\sqlservernamec$" and when prompted for credentials, I would give the domain account that the client has provided me and password and select the "Save password" checkbox. This would put these credentials in my saved credentials list for my user account. After doing this, I would be able to connect to the SQL Server via Windows Authentication in SSMS and Integrated Security (SSPI in connection strings) from applications (ASP and .Net). Everything worked happily with locked down SQL Servers and Windows Authentication.
Then comes Vista...
None of this works. It seems the stored credentials in Vista do not get honored when connecting to a SQL Server, other than the instance installed on my local machine. I have been able to connect to a remote instance via Named Pipes, but most of my clients have that disabled because of incompatibility with Distributed Transactions. So, I ask, is there any way to connect to a remote SQL Server instance (2000 or 2005) from Vista via TCP and Windows Authentication when the client Vista workstation is not in the same domain as the server?
I have tried so many things, I am not sure where to continue from. I have looked into setting SPNs for domain accounts, upgraded servers to latest service packs, etc.
Bottom line, this is the only thing i have found with SQL Server that ALWAYS worked in Windows XP does not work in Vista and, at this point, is getting close to being a killer causing me to go back to XP.
my VB6 programs that use ADO to access SQL or Access databases do not work in Windows Vista. While they run smoothly in all older Windows versions, they fail in Windows Vista environments. Especially, the ADO connection does not work anymore. The same connection strings that work perfectly in all older Windows versions, do not work in Windows Vista. The error message sent by ADO is this: Runtime error -2147217887 - "Multiple-step OLE DB operation generated errors". And, not only I get this error message on my development systems, but all other users of my programs on all Windows Vista systems.
I have been playing around with alternative connections strings, but no alternative works.
