Failed To Connect To SQL Server 2005 Database Form Microsoft Office Business Scorecard Manager 2005
Apr 17, 2007
Hi,all BI experts here,
Thank you very much for your kind attention.
I am having a problem with connecting to SQL Server 2005 database from Office Business Scorecard Manager 2005 (the connection string i am using is: provider=SQLOLEDB;Data source=server_name; Initial catalog=database_name). But the connection failed. Would please any experts here shed me any light on what is the problem and how to fix it then? As there is no any forum for Office Business Scrorecard manager 2005. Therefore I post my thread here as it is related to the connection to SQL Server 2005 database engine, thought here is the best place for this question.
Thank you very in advance for your kind advices and help. And I am looking forward to hearing from you soon.
With best regards,
Yours sincerely,
View 6 Replies
ADVERTISEMENT
Apr 25, 2007
Hi , all Microsoft BI experts here,
Thanks for your kind attention.
I am having a question as stated in the subject title, yes, when we want to deploy scorecards to reporting services, as the prerequisite, how can we install and register the scorecard custom data processing extension with the Microsoft reporting services server?
I am looking forward to hearing from you shortly and thank you again.
With best regards,
Yours sincerely,
View 1 Replies
View Related
Nov 15, 2005
I was trying to install Business Scorecard Manager Server , for that i have installed SQL server 2000, Analysis services and Service Pack 4 and also have taken mixed mode of authentication . Then i have installed sharepoint portal server 2003 and extended a site .
View 3 Replies
View Related
Aug 9, 2005
I installed Microsoft SQL Server 2005 Express Manager and connect to SQL 2000 normally
View 10 Replies
View Related
Dec 18, 2007
I'm green on this networking stuff so any help is greatly appreciated.
I have setup my home computer as a server and assigned a static IP to it. I installed SQL Server 2005 Developer and allowed remote connections to it through the Surface Area Config tool, added port 1433 TCP and 1434 UDP to firewall's exception list, and started the SQL Server Browser service.
Now I can't seem to remote connect to this SQL Server from my office network. Is there something I'm doing wrong here?
Thanks!!
View 3 Replies
View Related
Apr 25, 2008
hello,
I have a question about opening files in the Microsoft SQL Server 2005 Management Studio.
In the old Query Analyzer from SQL 2000 I can open SQL Files via drag & drop (from explorer to QA) or open it with a double click in the explorer. Then the Files opened, if I had actual a connection to a server / database (QA is stared with one file and has a connection to Server/Datebase), with this connection.
Now in Microsoft SQL Server 2005 Management Studio I'll be asked everytime for Server and have to get the database from the database list - it does not connect automaticly to server/database, that is actual connected (I have opened a file with the connection and a connected database in the object explorer).
Someone do not have this problem - but we found no option to set it up.
Any ideas?
thanks &
best regards,
Christian Kiedels
View 9 Replies
View Related
Jan 28, 2008
I'm looking for a little help on a strange problem, used Business Contact Manager 2007 Database Tool to create a shared database in SQL Server 2005 on a server on the LAN, placed the database in the default instance of MSSQLSERVER then used the database tools to restore a 2003 BCM database to the newly created database in SQL. Everything worked as it should and I verified the database existed and was populated with data and all the permissions were set correctly to access the database. Then I loaded 2007 Business Contact Manager on a workstation on the LAN and attempted to use the wizard to connect to the remote database. I keep receiving errors that the database cannot be found. I have used the SQLCMD (Sqlcmd €“S €śtcp:erverNameinstanceName,portNumber€?) to verify access to the server and named instance and can connect with no problem, so it appears that would eliminate any firewall (which I turned off) problem or permission problem on the SQL Server. This is a connection between a Vista computer and a Server 2003 domain controller. DNS appears to work without a problem as a ping from the Vista machine by server name yields the correct IP. I have several databases running on the sequel server and have no problem accessing them. Any help would be greatly appreciated.
View 3 Replies
View Related
Sep 18, 2006
I'm not experienced with SQL Server 2005.I've got a live copy of my database running on the web server.I've got another copy running on my desktop that I make changes to.Whats the best way to sync between the two so:1. I don't have to take the application offline2. I don't loose any data from the live database3. But I can implement changes to tables and/or add new tables
View 1 Replies
View Related
Mar 7, 2007
Hi all,
I'm a newbie to Reporting Services so please forgive my ignorance...
I've recently installed SQL Server Express 2005 with Reporting Services on my Vista Business Notebook (with no network connections) and have installed VS C# Express as well as the Business Intelligence Studio to create reports.
My C# application can connect to SQL Server fine, however, the reports I created with Business Studio refuses to deploy to the server due to the following reason:
"The permissions granted to user 'localhostJenny' are insufficient for
performing this operation".
I find this odd as I've been able to deploy reports on my other Windows XP machine (with SQL Server Express) no probs at all. Additionally, I cannot see the 'Site settings' link within Report Manager (Web) that I'd normally get with an admin account (i.e. on my Win. XP machine). Various sources indicate that my account has insufficient access rights to view this.
Having browsed through seemingly endless blogs and forums, I suspect that my local account has not been configured to access the Report Manager web client to publish, manage and administer the site.
I have tried the surface area tool for SQL Server, but I suspect that this is relevant only to SQL Server DB access and management. Adding an administrator here does nothing.
The question is, how can I grant access to myself (local account) to allow me to publish reports via business studio, and at the same time - administer Report Manager Site Settings - on my vista notebook??
I would be extremely grateful for any help on this matter - I've tried ceaseless reinstallations, but to no avail!
Many thanks in advance,
Jenny
View 5 Replies
View Related
Apr 23, 2008
Hello,
I am creating a windows application that is not going to be used in a controlled environment like a LAN or some other network, so I want to include a local database in the install of this app. Ideally, I would like to use SQL 2005 Express like you would MSDE or Access, but I am not sure if the user must have SQL Server installed on their machine in order for this to work and I don't have a machine without it to test on.
Any help on this is greatly appreciated.
Thanks,
Derek
View 1 Replies
View Related
Mar 3, 2008
hi,
i am getting the following error message while i am trying to login to the SQL Server 2005 on my vista laptop. i installed the server with dual authentication modes.
Login failed for the user'xxxx'(Microsoft SQL Server 2005. Error:18456)
if you have solution for my problem please send a reply as early as possible.
thanks,
ravi kishore.ch
View 12 Replies
View Related
Nov 18, 2005
I installed, uninstalled, deleted, editted my registry etc and I finally goto to this error while trying to install VS2005 (released) on a Windows 2000 PC (that had Beta2 and RC1 installed & uninstalled):
View 12 Replies
View Related
Aug 23, 2007
I have tried to install Outlook 2007 with BCM and recieve the error listed above. I have also included a copy of my log file. Any suggestions?
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Thu Aug 23 14:22:59 2007
Machine : MACBOOK
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
Error Number : 1603
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Aug 23 14:23:45 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SCC.log
View 3 Replies
View Related
Aug 16, 2007
Hi:
I have a SQL 2005 instance (standard edition with sp2 on windows 2003 server) located on different domain.
I can connect to it by using sa only. I need to use SQL login.
I created another user called 'test' and granted with sysadmin server role, but I got following error:
Login failed for user 'test'. (Microsoft SQL Server, Error: 18456)
I searched on the internet two days with no luck.
Any idea?
Thanks in advance.
Theresa
View 7 Replies
View Related
Jul 4, 2007
I Don't understand what this means: Everytime I try and install the disc 2 of my Office Small Business 2007, it gives the same message. Help.
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Tue Jul 03 17:14:45 2007
Machine : SWANNER-PC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
Error Number : 1618
--------------------------------------------------------------------------------
Machine : SWANNER-PC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
Error Number : 1618
--------------------------------------------------------------------------------
Machine : SWANNER-PC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
Error Number : 1618
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Tue Jul 03 17:15:12 2007
List of log files:
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core(Patched).log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Datastore.xml
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_.NET Framework 2.0.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Support.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SCC.log
View 38 Replies
View Related
Nov 21, 2006
I've used Sql Server 2000 and Visual Studio 2003 for a few years. I've started a new position and they have access to Sql Server 2005 Standard and Visual Basic 2005 Express which I'd like to use for a new project. So I installed Sql Server 2005 and then VB 2005 Express on my workstation. I didn't choose the Sql Server option for VB Express because I already had Sql Server 2005 Standard installed with a simple database created. I created a simple vb project that justs connects to the database but I get the following error.
Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0000, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
I looked at permissions in the database and it looks ok. I'm the db owner and I'm using Windows Auth. My connection string is
"Data Source=MySystem;initial catalog=AdventureWorks;integrated security=true;"
I thought I'd look at the starter kit to get some ideas about what the problem is, but when I started the movie starter kit project, it was upset that I didn't have Sql Server 2005 EXPRESS installed. Yea, but I do have Sql Server 2005 Standard installed.
Any help will be greatly appreciated. Thanks.
View 6 Replies
View Related
Mar 4, 2008
Hi all,I am trying to setup a VB.Net development environment on my desktop for one of the application which was already in the production for couple of years (some unknown contractor(s) developed and maintained it so far). The application works fine on the web.Visual Studio 2005, .Net 2.0, SQL 2000, SQL Server 2005 were installed on my desktop. When I try to build the entire application/solution in the debug mode (i.e., with http://localhost/), build succeeds and I could get to the login.aspx. When I try to login, I am getting an error in the Visual Studio at the following code;connection = New SqlConnection(connectionString)
connection.Open()
saying "Communication with the underlying transaction manager has failed", "System.Transactions.TransactionManagerCommunicationException was unhandled by user code". And the web browser displays the following error "Error HRESULT E_FAIL has been returned from a call to a COM component". When I try to connect the SQL Server 2005 with the same ConnectionString attributes by going to Tools>Connect to Database, it works fine. But, through application connection.Open() giving above errors. I have set the MSDTC properties (i.e., under Component Services>MyComputer Properties>Security Configuration) as below:-Enabled Network DTC Access, Allow Remote Clients, Allow Remote Administration, Allow Inbound, Allow Outbound, No Authentication required - selected, Enabled XA Transactions...& DTC Logon Account is "NT AUTHORITYNetworkService".Please help.Thanks in advance,Chandra
View 3 Replies
View Related
Mar 18, 2008
Hi,
I understand from previous threads that installing SQL Server 2005 Service Pack 2 on the desktop client can speed up the response rate of the Visual Studio 2005 Business Intelligence Tools.
However after logging on as an administrator and installing Service Pack 2, Service Pack 2 returned no errors. However after launching Visual Studio and clicking on the about dialog box the version reported was still €śRTM.050727-4200€? where I was expecting to see €śSP.050727-7600€?.
I understood that I applied the same service pack to my copy of SQL Server on my laptop and the upgrade worked successfully.
Can anyone help?
Thanks in advance,
Kieran.
View 9 Replies
View Related
May 7, 2008
I installed sql server 2005 sp2 including business intelligence development suite , however I got a message
some client components not compablitable .This morning I searched my programs and found that I have new
visual studio 2005 on my computer (before I just had vs 2008) as well as business intelligence
developer (which does not work) It seems I I would like to get rid of vs 2005 also
fix business intelligence studio . Previously I deleted vs 2005 express off my computer........(I have vista
and I would only like to keep tools meant for sql standard 2005 reporting services etc
here is a list of my sql sp2 install package
By the way I doubled clicked sql_tools.msi and did not run as administrator
Does that make a difference? I wonder if this is a problem with vs 2008 and sql 2005......
Time: 05/06/2008 20:49:23.437
KB Number: KB921896
Machine: BILLPREC690
OS Version: Professional (Build 6000)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.00.1399.06 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Analysis Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Reporting Services (MSSQLSERVER) ENU RTM 9.00.1399.00 x86 STANDARD
Notification Services ENU RTM 9.00.1399.00 x86 STANDARD
Integration Services ENU RTM 9.00.1399.00 x86 STANDARD
SQL Server Native Client ENU 9.00.3042.00 x86
Client Components ENU RTM 9.00.1399.06 x86 STANDARD
SQLXML4 ENU 9.00.1399.06 x86
Backward Compatibility ENU 8.05.1054 x86
Microsoft SQL Server VSS Writer ENU 9.00.1399.06 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
SQLWriter Microsoft SQL Server VSS Writer Service 2700
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 3010
Error Description :
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Reporting Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Notification Services
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 3010
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 1054
Product Version (Final) : 2004
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 1399
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
Success, Reboot Required
Exit Code Returned: 3010
View 2 Replies
View Related
Feb 26, 2008
Hi, i have created a database in business contact manager which is currently been used by five toher employees. I was trying to move that database to my server. Well I found this tool online called "Business contact manager 2007 database tool". I am trying to run it on the server but it is giving me a following error:
"Cannot retrive the list of SQL Server instances. Please make sure that SQL Server 2005 or SQL 2005 Express is installed and that the service is running."
I have SQL 2005 installed on my computer and I dont have any idea how to resolve this issue. It would be great if someone could help me.
View 1 Replies
View Related
Dec 17, 2007
Hi,
Is it possible to make Pivottables in Office 2000(Frontpage or Excel) and get data from cubes in Analyses Services SQL server 2005? If it works, are there any problems or do I have full functionality?
BR/Magnus
View 2 Replies
View Related
Feb 29, 2008
I am trying to use a new microsoft add-in for office 2007. I installed the 180 day trial version of SQL Server 2005 and according to the instructions it was suppose to be very easy to connect the add in to SQL. I am receiving an error message which I cannot find a resolution to using the readme file and wonder if you can help. Here is the url to the readme file and a screenshot with a summary of the add in.
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm#_3461_accessing_setup_documentation_cuy1
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/RequirementsSQL2005.htm
http://www.microsoft.com/sql/technologies/dm/addins.mspx
ERROR MESSAGE
Unable to connect to server 'localhost'. Please make sure user 'ARTIMUSArt McCarty' has at least read permission to some database on the server.
DETAILS ON TH ADDIN
The SQL Server 2005 Data Mining Add-ins for Office 2007 allow you to uncover hidden patterns and relationships in your data and then put them to work to enhance the quality of your analysis.
The package you downloaded allows you to install the following add-ins:
Table Analysis Tools for Excel
With a couple of mouse clicks you can detect and analyze the key influential factors for values in your data, highlight values that don't fit with the rest of the data. More
Data Mining Client for Excel
Go through the full data mining model development lifecycle within Excel by using your spreadsheet data, or by using external data accessible through your Analysis Services database. More
Data Mining Templates for Visio
Render and share your mining models as Visio drawings that you can annotate. More
Thanks for your help.
Art
View 1 Replies
View Related
Aug 7, 2007
i got this error msg when installing 2005 SQL Server components only on my system:
SQL Server Setup cannot continue because an earlier version of Office Web Components is installed on this computer. Uninstall Office Web Components, and then run installation again.
i could not find any info on this error. any ideas?
thanks for the help.
--Yasaman
View 6 Replies
View Related
Nov 3, 2006
I want to use SQL Server to query an Access Database with about 40,000 rows of data. If possible, I don't want to upsize the database because others need acess to it in the ACC97 format. Is there a way to use ODBC to connect to the ACC97 database so that I can use the SQL query capability of SQL server to query the database.
I know access allows you to write some SQL queries but I need the power of the SQL server and now it is a matter of curiosity because I've been searching for this answer for about 8 hours.
View 1 Replies
View Related
Nov 7, 2007
The following installation:
- Microsoft SQL Server 2005 Standard Edition running on Microsoft Windows Server 2003 Standard Edition
- Client Service for Netware installed.
- Access 2000 database in a Novell Directory Services (NDS) Environment
- SQL Server service running under local Administrator account.
Linked server configured as follow:
Linked server: MyDB
Provider: Microsoft Jet 4.0 OLE DB Provider
Product name: Access 2000
Data Source: UNC path to my Access database
Security: Admin with no password (default Access behaviour)
I can connect to my access database by following the next steps:
- Open Management studio on the SQL Server itself (where I'm logged in as Administrator)
- Connect using Windows Authentication (Administrator)
- Create a new query, run EXEC sp_tables_ex 'MyDB'
This will return all the tables from the Access database.
I can also make a view pointing to MyDB...MyTable.
Enough prove to me It can work....
So far so good
But now the tricky part.
When I login as 'sa', I can't connect and will receive the following message:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "MyDB" returned message "'Full UNC to my access database' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.".Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "MyDB".
(In real life I want to connect to my SQL 2005 Server from a ASP.NET (2.0) application using SQL authentication, but as long as I can't get the above working this is not important for now)
View 3 Replies
View Related
Sep 28, 2006
Everything was working fine. I have been able to connect using windows authentication. Then, I went into the ODBC manager to add a data source and it failed to connect so I went back into the Server management studio to modify users. After doing this I now get an error when I try to conenct the management studio to the SQL server.
I wasn't modifying the login for my windows account that I normally use, I was modifying a different one, however I now get the message "An error has occured while establishing a connection to the SQL server. This kind of problem can ocure because the default behavior of the server does not support all connection methods" blah blah.
Does anyone know how I can attach to the server? Or, do I need to somehow remove the server and create a new one? How would I do that?
Thanks in advance for any input.
View 1 Replies
View Related
Mar 3, 2008
after i installed sql server 2005 DM add-ins, i tried using it with office 2007 so i choose (start---->all programs----->microsoft sql 2005 dm add-ins---->getting started) so the getting started wizzard was opened, i selected from it (use an existing instance of microsoft sql server 2005 analysis services that i adminster) because i already had a version of it installed on my computer. then i tried to connect to analysis services by selecting 'server name'=local host, an error appeared which is "unable to discover meta data on the server 'local host' . user noha needs to be adminstrator of the server to run the configuration tool". how can i be the adminstrator of the server?????????.........plz reply me soon,thanks in advance
View 6 Replies
View Related
Mar 1, 2008
I am trying to use a new Excel microsoft add-in using SQL server 2005. I installed the 180 day trial version of SQL Server 2005 on my local machine and according to the instructions it was suppose to be very easy to connect the excel add in to SQL. I am receiving an error message which I cannot find a resolution to using the readme file and wonder if you can help.
ERROR MESSAGE
Unable to connect to server 'localhost'. Please make sure user 'ARTIMUS' has at least read permission to some database on the server.
THanks for your help!
Art
View 6 Replies
View Related
Jun 25, 2007
Hi
im trying to connect to sqlserver 2005 using windows authentication and gives me this error "Login failed for user ''. The user is not associated with a trusted SQL Server connection."
any help
thanks in advance.
View 3 Replies
View Related
Feb 2, 2007
I am update/inserting records threw a web form in vb.net. I need to insert 'NULL' into my microsoft sql server database. I am not talking about the below line of code where website is the name of my paramater. If i do that it will just place a blank into that field in the database. If i dont enter anything into that textbox I want it to to say NULL in that field. So if I go into the actual table in the SQL Server Management Studio and look at the website field of the recored I just added or updated and did not type anything into the web site textbox it needs to say NULL. I also tried the second line of code but that places a single quote in front and behind NULL. So the field will have the value 'NULL'.
website.value = txtwebsite.text.tostirng
if txtwebsite.text ="" then
website.value ="NULL"
end if
The reason why I need the NULL there is because I bind the website filed to a hyperlink template in a gridview. The actual text of the hyperlink is bound to PAYER which is a name of a insurance payer but the navigateto is bound to the website field. If i do not enter any data into the website field and it stays as NULL, then when my gridview is loaded, payers that dont have a website will not be underlined and user wont have the option to click on them since there is no value for the navigateto. But if i use my form to update/add a payer and leave the website textbox blank in puts a blank into that field in my database and when it loads that new row into the gridview the PAYER is underlined and u can click on it but it will just take u to the web site is unavailable page. So is there anyway to actaull have NULL placed into a filed and not just blank space
View 3 Replies
View Related
May 16, 2007
Sp2 cannot be install
can someone help me
this is hotfix log
05/16/2007 13:05:30.583 ================================================================================
05/16/2007 13:05:30.599 Hotfix package launched
05/16/2007 13:05:30.630 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.646 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:30.662 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.677 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:30.693 Local Computer:
05/16/2007 13:05:30.708 Target Details: DC-01
05/16/2007 13:05:30.724 commonfilesdir = C:ProgrammiFile comuni
05/16/2007 13:05:30.740 lcidsupportdir = e:3f798aa49a0102c6d1f049aa36bd359d1040
05/16/2007 13:05:30.755 programfilesdir = C:Programmi
05/16/2007 13:05:30.771 programfilesdir_wow = C:Programmi
05/16/2007 13:05:30.771 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.802 supportdirlocal = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.818 windir = C:WINDOWS
05/16/2007 13:05:30.833 winsysdir = C:WINDOWSsystem32
05/16/2007 13:05:30.849 winsysdir_wow = C:WINDOWSSysWOW64
05/16/2007 13:05:30.865
05/16/2007 13:05:30.958 Enumerating applicable products for this patch
05/16/2007 13:05:31.005 Found Redist 2005 product definition
05/16/2007 13:05:31.021 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.036 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.052 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.068 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.442 Found Redist 2005 product definition
05/16/2007 13:05:31.458 Found Redist 2005 product definition
05/16/2007 13:05:31.474 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.489 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.505 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.521 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.677 Found SQL 2005 product definition
05/16/2007 13:05:32.270 Enumeration: Determining QFE level for product instance MSSQLSERVER
05/16/2007 13:05:32.286 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.286 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
05/16/2007 13:05:32.302 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
05/16/2007 13:05:32.317 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.333 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
05/16/2007 13:05:32.348 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.348 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:32.364 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.380 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:32.395 Product discovery completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 SP Level check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 Product language check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.426 Product version check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.442 Command-line instance name check completed during the install process
05/16/2007 13:05:32.458 SKU check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.473 Baseline build check completed during the installation process for MSSQLSERVER
05/16/2007 13:05:32.489 Baseline build check completed during the install process
05/16/2007 13:05:32.505 Found OLAP Server 2005 product definition
05/16/2007 13:05:33.004 Command-line instance name check completed during the install process
05/16/2007 13:05:33.004 Baseline build check completed during the install process
05/16/2007 13:05:33.036 Found Notification Services 2005 product definition
05/16/2007 13:05:33.520 Baseline build check completed during the install process
05/16/2007 13:05:33.551 Found Report Server 2005 product definition
05/16/2007 13:05:34.051 Command-line instance name check completed during the install process
05/16/2007 13:05:34.066 Baseline build check completed during the install process
05/16/2007 13:05:34.082 Found DTS 2005 product definition
05/16/2007 13:05:34.582 Baseline build check completed during the install process
05/16/2007 13:05:34.613 Found SQL 2005 Tools product definition
05/16/2007 13:05:35.113 Enumeration: Determining GDR branching Hotfix for product instance
05/16/2007 13:05:35.144 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
05/16/2007 13:05:35.160 Enumeration: No GDR branch Hotfix found for product instance
05/16/2007 13:05:35.175 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.191 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.207 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.207 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.222 Product discovery completed during the install process for SQL Tools
05/16/2007 13:05:35.238 SP Level check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product language check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product version check completed during the install process for SQL Tools
05/16/2007 13:05:35.269 SKU check completed during the install process for SQL Tools
05/16/2007 13:05:35.285 Baseline build check completed during the install process
05/16/2007 13:05:35.300 Found Redist 2005 product definition
05/16/2007 13:05:35.316 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.332 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.347 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.363 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.597 Found Redist 2005 product definition
05/16/2007 13:05:35.613 Found Redist 2005 product definition
05/16/2007 13:05:35.628 Found Redist 2005 product definition
05/16/2007 13:05:35.644 Found Redist 2005 product definition
05/16/2007 13:05:35.660 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.675 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.675 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.691 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.909 Found Redist 2005 product definition
05/16/2007 13:05:35.925 Found Redist 2005 product definition
05/16/2007 13:05:35.941 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.941 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.956 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.972 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:36.128 Found Redist 2005 product definition
05/16/2007 13:05:36.191 Product Enumeration Results:
05/16/2007 13:05:36.206 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli.inf
05/16/2007 13:05:36.222 baselinebuild = 1399
05/16/2007 13:05:36.237 build = 3042
05/16/2007 13:05:36.253 description = SQL Server Native Client
05/16/2007 13:05:36.269 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.284 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.300 kbarticle = KB921896
05/16/2007 13:05:36.316 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.331 lcid = 1040
05/16/2007 13:05:36.347 legalproductname = Microsoft SQL Native Client
05/16/2007 13:05:36.362 machinetype = x86
05/16/2007 13:05:36.362 package = HotFixSqlncli
05/16/2007 13:05:36.378 packagetype = Hotfix
05/16/2007 13:05:36.394 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.409 productname = Redist9
05/16/2007 13:05:36.425 recommendinstall = 1
05/16/2007 13:05:36.441 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:36.456 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:36.472 splevel = 2
05/16/2007 13:05:36.487 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:36.519 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:36.519 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
05/16/2007 13:05:36.534 version = 9
05/16/2007 13:05:36.550
05/16/2007 13:05:36.581 File Group Details: MSI
05/16/2007 13:05:36.597 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:36.612 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:36.628 File Details: sqlncli.msi
05/16/2007 13:05:36.644
05/16/2007 13:05:36.659 Instance Details: SQL Server Native Client
05/16/2007 13:05:36.690 fullversion = 9.00.3042.00
05/16/2007 13:05:36.706 lcid = 1040
05/16/2007 13:05:36.722 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.753 qfelevel = 3042
05/16/2007 13:05:36.769 sp = -1
05/16/2007 13:05:36.784
05/16/2007 13:05:36.800 Product Enumeration Results:
05/16/2007 13:05:36.831 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli_x64.inf
05/16/2007 13:05:36.847 baselinebuild = 1399
05/16/2007 13:05:36.862 build = 3042
05/16/2007 13:05:36.878 description = SQL Server Native Client
05/16/2007 13:05:36.893 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.909 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.940 kbarticle = KB921896
05/16/2007 13:05:36.956 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.972 lcid = 1040
05/16/2007 13:05:36.987 legalproductname = Microsoft SQL Native Client (64 bit)
05/16/2007 13:05:37.018 machinetype = x64
05/16/2007 13:05:37.034 package = HotFixSqlncli_x64
05/16/2007 13:05:37.050 packagetype = Hotfix
05/16/2007 13:05:37.081 productname = Redist9
05/16/2007 13:05:37.097 recommendinstall = 1
05/16/2007 13:05:37.112 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.128 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.159 splevel = 2
05/16/2007 13:05:37.175 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.190 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
05/16/2007 13:05:37.206 version = 9
05/16/2007 13:05:37.237
05/16/2007 13:05:37.253 File Group Details: MSI
05/16/2007 13:05:37.268 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:37.284 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.315 File Details: sqlncli_x64.msi
05/16/2007 13:05:37.331
05/16/2007 13:05:37.346 Product Enumeration Results:
05/16/2007 13:05:37.362 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlSupport.inf
05/16/2007 13:05:37.393 alwaysinstall = 1
05/16/2007 13:05:37.409 baselinebuild = 1399
05/16/2007 13:05:37.425 build = 3042
05/16/2007 13:05:37.456 description = File di supporto dell'installazione
05/16/2007 13:05:37.534 details = Service Pack per i file di supporto dell'installazione di SQL Server.
05/16/2007 13:05:37.565 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:37.581 kbarticle = KB921896
05/16/2007 13:05:37.596 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:37.612 keyqualifier = 1
05/16/2007 13:05:37.643 lcid = 1040
05/16/2007 13:05:37.659 legalproductname = File di supporto dell'installazione di SQL Server 2005
05/16/2007 13:05:37.674 machinetype = x86
05/16/2007 13:05:37.690 package = HotFixSqlSupport
05/16/2007 13:05:37.690 packagetype = Hotfix
05/16/2007 13:05:37.706 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:37.737 productname = Redist9
05/16/2007 13:05:37.753 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.768 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.784 splevel = 2
05/16/2007 13:05:37.815 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:37.831 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.846 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
05/16/2007 13:05:37.862 version = 9
05/16/2007 13:05:37.877
05/16/2007 13:05:37.893 File Group Details: MSI
05/16/2007 13:05:37.909 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
05/16/2007 13:05:37.940 parameters = REINSTALL=ALL
05/16/2007 13:05:37.956 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.971 File Details: SqlSupport.msi
05/16/2007 13:05:37.987
05/16/2007 13:05:38.002 Instance Details: File di supporto dell'installazione
05/16/2007 13:05:38.018 fullversion = 9.2.3042
05/16/2007 13:05:38.049 lcid = 1040
05/16/2007 13:05:38.065 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:38.081 qfelevel = 3042
05/16/2007 13:05:38.096 sp = -1
05/16/2007 13:05:38.112
05/16/2007 13:05:38.143 Product Enumeration Results:
05/16/2007 13:05:38.159 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQL.inf
05/16/2007 13:05:38.174 baselinebuild = 1399
05/16/2007 13:05:38.190 baselinebuildmax = 3042
05/16/2007 13:05:38.205 build = 3042
05/16/2007 13:05:38.221 description = Servizi di database
05/16/2007 13:05:38.237 details = Service Pack per il Motore di database e gli strumenti di SQL Server per la gestione di dati relazionali e XML, per la replica e per la ricerca full-text.
05/16/2007 13:05:38.252 installer = Hotfix
05/16/2007 13:05:38.268 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:38.284 kbarticle = KB921896
05/16/2007 13:05:38.299 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:38.330 lcid = 1040
05/16/2007 13:05:38.346 legalproductname = Servizi di database SQL Server 2005
05/16/2007 13:05:38.362 machinetype = x86
05/16/2007 13:05:38.393 package = HotFixSQL
05/16/2007 13:05:38.409 packagetype = Hotfix
05/16/2007 13:05:38.424 productname = SQL9
05/16/2007 13:05:38.440 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:38.471 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:38.487 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:38.502 splevel = 2
05/16/2007 13:05:38.518 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:38.549 sqlutility = sqlcmd.exe
05/16/2007 13:05:38.565 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:38.580 validateauthentication = true
05/16/2007 13:05:38.596 version = 9
05/16/2007 13:05:38.612
05/16/2007 13:05:38.627 File Group Details: MSP
05/16/2007 13:05:38.658 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:38.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:38.690 File Details: sqlrun_sql.msp
05/16/2007 13:05:38.705
05/16/2007 13:05:38.721 Instance Details: MSSQLSERVER
05/16/2007 13:05:38.752 agentservicename = SQLSERVERAGENT
05/16/2007 13:05:38.768 clustername =
05/16/2007 13:05:38.783 default = TRUE
05/16/2007 13:05:38.815 ftsservicename = MSFTESQL
05/16/2007 13:05:38.830 fullversion = 2005.090.1399.00
05/16/2007 13:05:38.846 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
05/16/2007 13:05:38.877 id = MSSQL.1
05/16/2007 13:05:38.893 installsqldatadir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.908 installsqldir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.924 lcid = 1040
05/16/2007 13:05:38.940 name = MSSQLSERVER
05/16/2007 13:05:38.971 productcode = {E0BB3923-308B-4BE9-B3A3-FD5517481E48}
05/16/2007 13:05:39.002 qfelevel = 1399
05/16/2007 13:05:39.018 servicename = MSSQLServer
05/16/2007 13:05:39.033 sku = STANDARD
05/16/2007 13:05:39.049 sp = 0
05/16/2007 13:05:39.065 type = SQL Server Standalone Product
05/16/2007 13:05:39.096 vermajbld = 1399
05/16/2007 13:05:39.111 version = 9
05/16/2007 13:05:39.127
05/16/2007 13:05:39.143 Product Enumeration Results:
05/16/2007 13:05:39.174 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixAS.inf
05/16/2007 13:05:39.189 baselinebuild = 1399
05/16/2007 13:05:39.205 baselinebuildmax = 3042
05/16/2007 13:05:39.236 build = 3042
05/16/2007 13:05:39.252 description = Analysis Services
05/16/2007 13:05:39.268 details = Service Pack per Analysis Services e per gli strumenti per il supporto dell'elaborazione analitica in linea (OLAP) e del data mining.
05/16/2007 13:05:39.283 installer = Hotfix
05/16/2007 13:05:39.299 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.330 kbarticle = KB921896
05/16/2007 13:05:39.346 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.361 lcid = 1040
05/16/2007 13:05:39.377 legalproductname = SQL Server Analysis Services 2005
05/16/2007 13:05:39.408 machinetype = x86
05/16/2007 13:05:39.424 package = HotFixAS
05/16/2007 13:05:39.455 packagetype = Hotfix
05/16/2007 13:05:39.471 productname = OLAP9
05/16/2007 13:05:39.486 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:39.502 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:39.533 splevel = 2
05/16/2007 13:05:39.549 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:39.564 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:39.580 version = 9
05/16/2007 13:05:39.611
05/16/2007 13:05:39.627 File Group Details: MSP
05/16/2007 13:05:39.642 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:39.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:39.689 File Details: sqlrun_as.msp
05/16/2007 13:05:39.705
05/16/2007 13:05:39.736 Product Enumeration Results:
05/16/2007 13:05:39.752 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixNS.inf
05/16/2007 13:05:39.767 baselinebuild = 1399
05/16/2007 13:05:39.799 baselinebuildmax = 3042
05/16/2007 13:05:39.814 build = 3042
05/16/2007 13:05:39.830 description = Notification Services
05/16/2007 13:05:39.861 details = Service Pack per Notification Services, una piattaforma per lo sviluppo e la distribuzione di applicazioni per l'invio di notifiche personalizzate e tempestive a un'ampia gamma di dispositivi o applicazioni.
05/16/2007 13:05:39.877 installer = Hotfix
05/16/2007 13:05:39.892 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.908 kbarticle = KB921896
05/16/2007 13:05:39.924 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.939 lcid = 1040
05/16/2007 13:05:39.970 legalproductname = Istanze di SQL Server Notification Services 2005
05/16/2007 13:05:39.986 machinetype = x86
05/16/2007 13:05:40.002 package = HotFixNS
05/16/2007 13:05:40.017 packagetype = Hotfix
05/16/2007 13:05:40.033 productname = NS9
05/16/2007 13:05:40.064 recommendinstall = 1
05/16/2007 13:05:40.080 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.095 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.111 splevel = 2
05/16/2007 13:05:40.142 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.158 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.189 version = 9
05/16/2007 13:05:40.205
05/16/2007 13:05:40.220 File Group Details: MSP
05/16/2007 13:05:40.236 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.267 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.283 File Details: sqlrun_ns.msp
05/16/2007 13:05:40.298
05/16/2007 13:05:40.330 Product Enumeration Results:
05/16/2007 13:05:40.345 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixRS.inf
05/16/2007 13:05:40.361 baselinebuild = 1399
05/16/2007 13:05:40.376 baselinebuildmax = 3042
05/16/2007 13:05:40.408 build = 3042
05/16/2007 13:05:40.423 description = Reporting Services
05/16/2007 13:05:40.439 details = Service Pack per Server report e Generatore report, utilizzati per la gestione, l'esecuzione, il rendering e la distribuzione dei report.
05/16/2007 13:05:40.455 installer = Hotfix
05/16/2007 13:05:40.486 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:40.501 kbarticle = KB921896
05/16/2007 13:05:40.517 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:40.548 lcid = 1040
05/16/2007 13:05:40.564 legalproductname = SQL Server Reporting Services 2005
05/16/2007 13:05:40.580 machinetype = x86
05/16/2007 13:05:40.611 package = HotFixRS
05/16/2007 13:05:40.626 packagetype = Hotfix
05/16/2007 13:05:40.642 productname = RS9
05/16/2007 13:05:40.658 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.673 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.689 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:40.720 splevel = 2
05/16/2007 13:05:40.736 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.751 sqlutility = sqlcmd.exe
05/16/2007 13:05:40.767 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.798 validateauthentication = 1
05/16/2007 13:05:40.814 version = 9
05/16/2007 13:05:40.829
05/16/2007 13:05:40.861 File Group Details: MSP
05/16/2007 13:05:40.876 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.892 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.908 File Details: sqlrun_rs.msp
05/16/2007 13:05:40.939
05/16/2007 13:05:40.954 Product Enumeration Results:
05/16/2007 13:05:40.970 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixDTS.inf
05/16/2007 13:05:41.001 baselinebuild = 1399
05/16/2007 13:05:41.017 baselinebuildmax = 3042
05/16/2007 13:05:41.032 build = 3042
05/16/2007 13:05:41.064 description = Integration Services
05/16/2007 13:05:41.079 details = Service Pack per Integration Services, una serie di strumenti e oggetti programmabili per la creazione e la gestione di pacchetti per l'estrazione, la trasformazione e il caricamento dei dati, nonché per l'esecuzione di attività .
05/16/2007 13:05:41.095 installer = Hotfix
05/16/2007 13:05:41.126 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.142 kbarticle = KB921896
05/16/2007 13:05:41.157 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.173 lcid = 1040
05/16/2007 13:05:41.189 legalproductname = SQL Server Integration Services 2005
05/16/2007 13:05:41.220 machinetype = x86
05/16/2007 13:05:41.236 package = HotFixDTS
05/16/2007 13:05:41.251 packagetype = Hotfix
05/16/2007 13:05:41.282 productname = DTS9
05/16/2007 13:05:41.298 recommendinstall = 1
05/16/2007 13:05:41.314 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.329 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.360 splevel = 2
05/16/2007 13:05:41.376 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:41.392 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:41.423 version = 9
05/16/2007 13:05:41.439
05/16/2007 13:05:41.454 File Group Details: MSP
05/16/2007 13:05:41.485 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:41.501 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:41.517 File Details: sqlrun_dts.msp
05/16/2007 13:05:41.548
05/16/2007 13:05:41.564 Product Enumeration Results:
05/16/2007 13:05:41.579 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixTools.inf
05/16/2007 13:05:41.610 baselinebuild = 1399
05/16/2007 13:05:41.626 baselinebuildmax = 3042
05/16/2007 13:05:41.642 build = 3042
05/16/2007 13:05:41.657 description = Componenti client
05/16/2007 13:05:41.688 details = Service Pack per gli strumenti interattivi di gestione per l'esecuzione di SQL Server, tra cui Gestione configurazione SQL Server, SQL Server Management Studio, SQL Profiler e Monitoraggio replica.
05/16/2007 13:05:41.704 installer = Hotfix
05/16/2007 13:05:41.720 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.751 kbarticle = KB921896
05/16/2007 13:05:41.767 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.782 lcid = 1040
05/16/2007 13:05:41.798 legalproductname = Componenti workstation e strumenti di SQL Server 2005
05/16/2007 13:05:41.829 machinetype = x86
05/16/2007 13:05:41.845 package = HotFixTools
05/16/2007 13:05:41.860 packagetype = Hotfix
05/16/2007 13:05:41.876 productname = SQLTools9
05/16/2007 13:05:41.892 recommendinstall = 1
05/16/2007 13:05:41.923 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.938 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.954 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:41.985 splevel = 2
05/16/2007 13:05:42.001 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.016 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.032 version = 9
05/16/2007 13:05:42.063
05/16/2007 13:05:42.079 File Group Details: MSP
05/16/2007 13:05:42.095 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:42.110 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:42.141 File Details: sqlrun_tools.msp
05/16/2007 13:05:42.157
05/16/2007 13:05:42.188 Instance Details: SQL Tools
05/16/2007 13:05:42.204 associatedhotfixbuild = 1520
05/16/2007 13:05:42.220 clustername =
05/16/2007 13:05:42.235 fullversion = 9.2.3042
05/16/2007 13:05:42.266 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
05/16/2007 13:05:42.282 id =
05/16/2007 13:05:42.298 installsqldatadir =
05/16/2007 13:05:42.313 installsqldir = C:ProgrammiMicrosoft SQL Server90Tools
05/16/2007 13:05:42.329 lcid = 1040
05/16/2007 13:05:42.360 name =
05/16/2007 13:05:42.376 productcode = {B03FBBA3-CCE4-40CC-A0F1-01F952E7EB3E}
05/16/2007 13:05:42.391 qfelevel = 3042
05/16/2007 13:05:42.407 sku = STANDARD
05/16/2007 13:05:42.438 sp = 2
05/16/2007 13:05:42.454 type = Tools Only
05/16/2007 13:05:42.469 vermajbld = 3042
05/16/2007 13:05:42.501 version = 9
05/16/2007 13:05:42.516
05/16/2007 13:05:42.532 Product Enumeration Results:
05/16/2007 13:05:42.563 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6.inf
05/16/2007 13:05:42.579 baselinebuild = 1399
05/16/2007 13:05:42.594 build = 6.10.1129.0
05/16/2007 13:05:42.626 description = Parser MSXML 6.0
05/16/2007 13:05:42.641 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:42.657 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:42.688 kbarticle = KB921896
05/16/2007 13:05:42.704 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:42.719 lcid = 1040
05/16/2007 13:05:42.751 legalproductname = Parser MSXML 6.0
05/16/2007 13:05:42.766 machinetype = x86
05/16/2007 13:05:42.782 package = HotFixMsxml6
05/16/2007 13:05:42.797 packagetype = Hotfix
05/16/2007 13:05:42.813 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:42.844 productname = Redist9
05/16/2007 13:05:42.860 recommendinstall = 1
05/16/2007 13:05:42.876 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:42.891 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:42.922 splevel = 2
05/16/2007 13:05:42.938 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.969 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.985 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
05/16/2007 13:05:43.000 version = 9
05/16/2007 13:05:43.016
05/16/2007 13:05:43.032 File Group Details: MSI
05/16/2007 13:05:43.063 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.079 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.094 File Details: msxml6.msi
05/16/2007 13:05:43.110
05/16/2007 13:05:43.141 Instance Details: Parser MSXML 6.0
05/16/2007 13:05:43.157 fullversion = 6.10.1129.0
05/16/2007 13:05:43.172 lcid = 1040
05/16/2007 13:05:43.188 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:43.219 qfelevel = 1129
05/16/2007 13:05:43.235 sp = -1
05/16/2007 13:05:43.250
05/16/2007 13:05:43.266 Product Enumeration Results:
05/16/2007 13:05:43.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6_x64.inf
05/16/2007 13:05:43.313 baselinebuild = 1399
05/16/2007 13:05:43.328 build = 6.10.1129.0
05/16/2007 13:05:43.360 description = Parser MSXML 6.0
05/16/2007 13:05:43.375 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:43.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.422 kbarticle = KB921896
05/16/2007 13:05:43.438 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.453 lcid = 1040
05/16/2007 13:05:43.469 legalproductname = Parser MSXML 6.0 (64 bit)
05/16/2007 13:05:43.500 machinetype = x64
05/16/2007 13:05:43.516 package = HotFixMsxml6_x64
05/16/2007 13:05:43.532 packagetype = Hotfix
05/16/2007 13:05:43.563 productname = Redist9
05/16/2007 13:05:43.578 recommendinstall = 1
05/16/2007 13:05:43.594 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:43.610 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:43.625 splevel = 2
05/16/2007 13:05:43.641 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:43.656 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
05/16/2007 13:05:43.672 version = 9
05/16/2007 13:05:43.688
05/16/2007 13:05:43.703 File Group Details: MSI
05/16/2007 13:05:43.719 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.735 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.750 File Details: msxml6_x64.msi
05/16/2007 13:05:43.781
05/16/2007 13:05:43.797 Product Enumeration Results:
05/16/2007 13:05:43.813 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4.inf
05/16/2007 13:05:43.828 baselinebuild = 1399
05/16/2007 13:05:43.844 build = 3042
05/16/2007 13:05:43.860 description = SQLXML4
05/16/2007 13:05:43.875 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:43.891 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.906 kbarticle = KB921896
05/16/2007 13:05:43.922 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.938 lcid = 1040
05/16/2007 13:05:43.953 legalproductname = SQLXML4
05/16/2007 13:05:43.969 machinetype = x86
05/16/2007 13:05:43.984 package = HotFixSqlxml4
05/16/2007 13:05:44.000 packagetype = Hotfix
05/16/2007 13:05:44.016 productname = Redist9
05/16/2007 13:05:44.047 recommendinstall = 1
05/16/2007 13:05:44.063 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.078 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.094 splevel = 2
05/16/2007 13:05:44.109 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:44.125 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.141 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
05/16/2007 13:05:44.156 version = 9
05/16/2007 13:05:44.172
05/16/2007 13:05:44.188 File Group Details: MSI
05/16/2007 13:05:44.203 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.219 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.234 File Details: sqlxml4.msi
05/16/2007 13:05:44.266
05/16/2007 13:05:44.281 Product Enumeration Results:
05/16/2007 13:05:44.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4_x64.inf
05/16/2007 13:05:44.312 baselinebuild = 1399
05/16/2007 13:05:44.328 build = 3042
05/16/2007 13:05:44.344 description = SQLXML4
05/16/2007 13:05:44.375 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:44.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.391 kbarticle = KB921896
05/16/2007 13:05:44.422 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.422 lcid = 1040
05/16/2007 13:05:44.437 legalproductname = SQLXML4 (64 bit)
05/16/2007 13:05:44.453 machinetype = x64
05/16/2007 13:05:44.469 package = HotFixSqlxml4_x64
05/16/2007 13:05:44.484 packagetype = Hotfix
05/16/2007 13:05:44.500 productname = Redist9
05/16/2007 13:05:44.516 recommendinstall = 1
05/16/2007 13:05:44.531 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.547 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.562 splevel = 2
05/16/2007 13:05:44.594 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.609 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
05/16/2007 13:05:44.625 version = 9
05/16/2007 13:05:44.640
05/16/2007 13:05:44.656 File Group Details: MSI
05/16/2007 13:05:44.672 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.687 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.703 File Details: sqlxml4_x64.msi
05/16/2007 13:05:44.719
05/16/2007 13:05:44.734 Product Enumeration Results:
05/16/2007 13:05:44.750 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC.inf
05/16/2007 13:05:44.765 baselinebuild = 1399
05/16/2007 13:05:44.781 build = 2004
05/16/2007 13:05:44.797 description = CompatibilitĂ con le versioni precedenti
05/16/2007 13:05:44.812 details = Service Pack per i componenti per la compatibilitĂ con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:44.828 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.844 kbarticle = KB921896
05/16/2007 13:05:44.859 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.875 lcid = 1040
05/16/2007 13:05:44.890 legalproductname = CompatibilitĂ con le versioni precedenti a Microsoft SQL Server 2005
05/16/2007 13:05:44.906 machinetype = x86
05/16/2007 13:05:44.922 package = HotFixSQLServer2005_BC
05/16/2007 13:05:44.937 packagetype = Hotfix
05/16/2007 13:05:44.953 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:44.968 productname = Redist9
05/16/2007 13:05:44.984 recommendinstall = 1
05/16/2007 13:05:45.015 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.031 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.047 splevel = 2
05/16/2007 13:05:45.062 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:45.078 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.093 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
05/16/2007 13:05:45.109 version = 9
05/16/2007 13:05:45.125
05/16/2007 13:05:45.140 File Group Details: MSI
05/16/2007 13:05:45.171 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.187 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.203 File Details: SQLServer2005_BC.msi
05/16/2007 13:05:45.203
05/16/2007 13:05:45.218 Instance Details: CompatibilitĂ con le versioni precedenti
05/16/2007 13:05:45.234 fullversion = 8.05.2004
05/16/2007 13:05:45.250 lcid = 1040
05/16/2007 13:05:45.265 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:45.281 qfelevel = 2004
05/16/2007 13:05:45.296 sp = -1
05/16/2007 13:05:45.312
05/16/2007 13:05:45.328 Product Enumeration Results:
05/16/2007 13:05:45.343 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC_x64.inf
05/16/2007 13:05:45.375 baselinebuild = 1399
05/16/2007 13:05:45.375 build = 2004
05/16/2007 13:05:45.390 description = CompatibilitĂ con le versioni precedenti
05/16/2007 13:05:45.406 details = Service Pack per i componenti per la compatibilitĂ con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:45.421 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.453 kbarticle = KB921896
05/16/2007 13:05:45.453 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.468 lcid = 1040
05/16/2007 13:05:45.484 legalproductname = CompatibilitĂ con le versioni precedenti a Microsoft SQL Server 2005 (64 bit)
05/16/2007 13:05:45.500 machinetype = x64
05/16/2007 13:05:45.515 package = HotFixSQLServer2005_BC_x64
05/16/2007 13:05:45.531 packagetype = Hotfix
05/16/2007 13:05:45.546 productname = Redist9
05/16/2007 13:05:45.562 recommendinstall = 1
05/16/2007 13:05:45.578 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.593 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.609 splevel = 2
05/16/2007 13:05:45.624 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.640 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
05/16/2007 13:05:45.656 version = 9
05/16/2007 13:05:45.671
05/16/2007 13:05:45.703 File Group Details: MSI
05/16/2007 13:05:45.718 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.734 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.749 File Details: SQLServer2005_BC_x64.msi
05/16/2007 13:05:45.765
05/16/2007 13:05:45.781 Product Enumeration Results:
05/16/2007 13:05:45.796 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter.inf
05/16/2007 13:05:45.812 baselinebuild = 1399
05/16/2007 13:05:45.828 build = 3042
05/16/2007 13:05:45.843 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.874 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:45.890 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.906 kbarticle = KB921896
05/16/2007 13:05:45.921 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.937 lcid = 1040
05/16/2007 13:05:45.953 legalproductname = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.968 machinetype = x86
05/16/2007 13:05:45.984 package = HotFixSqlWriter
05/16/2007 13:05:45.999 packagetype = Hotfix
05/16/2007 13:05:46.015 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.031 productname = Redist9
05/16/2007 13:05:46.062 recommendinstall = 1
05/16/2007 13:05:46.078 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.093 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.109 splevel = 2
05/16/2007 13:05:46.124 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:46.140 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.156 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
05/16/2007 13:05:46.171 version = 9
05/16/2007 13:05:46.187
05/16/2007 13:05:46.203 File Group Details: MSI
05/16/2007 13:05:46.218 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.234 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.249 File Details: SqlWriter.msi
05/16/2007 13:05:46.281
05/16/2007 13:05:46.296 Instance Details: Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.312 fullversion = 9.00.3042.00
05/16/2007 13:05:46.328 lcid = 1040
05/16/2007 13:05:46.328 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.359 qfelevel = 3042
05/16/2007 13:05:46.374 sp = -1
05/16/2007 13:05:46.390
05/16/2007 13:05:46.406 Product Enumeration Results:
05/16/2007 13:05:46.421 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter_x64.inf
05/16/2007 13:05:46.437 baselinebuild = 1399
05/16/2007 13:05:46.453 build = 3042
05/16/2007 13:05:46.468 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.484 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:46.499 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:46.515 kbarticle = KB921896
05/16/2007 13:05:46.546 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:46.562 lcid = 1040
05/16/2007 13:05:46.577 legalproductname = Microsoft SQL Server VSS Writer (64 bit)
05/16/2007 13:05:46.593 machinetype = x64
05/16/2007 13:05:46.609 package = HotFixSqlWriter_x64
05/16/2007 13:05:46.640 packagetype = Hotfix
05/16/2007 13:05:46.656 productname = Redist9
05/16/2007 13:05:46.671 recommendinstall = 1
05/16/2007 13:05:46.687 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.718 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.734 splevel = 2
05/16/2007 13:05:46.749 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.781 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
05/16/2007 13:05:46.796 version = 9
05/16/2007 13:05:46.796
05/16/2007 13:05:46.827 File Group Details: MSI
05/16/2007 13:05:46.843 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.859 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.874 File Details: SqlWriter_x64.msi
05/16/2007 13:05:46.890
05/16/2007 13:05:57.967 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
05/16/2007 13:05:57.967 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:57.982 Multi-string values:
05/16/2007 13:05:57.998 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:58.014 Multi-string values:
05/16/2007 13:05:58.029 ??e:1971703f8a5eaa69b207
05/16/2007 13:05:58.045 PFR Check: PFR was found, but no files to be serviced were being referenced
05/16/2007 13:06:18.980 Authenticating user using SAPWD
05/16/2007 13:06:18.995 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:19.011 Starting service: MSSQLServer
05/16/2007 13:06:23.666 Started service: MSSQLServer
05/16/2007 13:06:23.729 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:24.323 User authentication failed
05/16/2007 13:06:24.354 Messaggio 18456, livello 14, stato 1, server DC-01, riga 1
05/16/2007 13:06:24.385 Accesso non riuscito per l'utente 'sa'.
05/16/2007 13:06:24.416 Stopping service: MSSQLServer
05/16/2007 13:06:26.432 Stopped service: MSSQLServer
05/16/2007 13:06:29.978 Authenticating user using Windows Authentication
05/16/2007 13:06:29.994 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:30.009 Starting service: MSSQLServer
05/16/2007 13:06:34.837 Started service: MSSQLServer
05/16/2007 13:06:34.931 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:35.462 Authenticating user using Windows Authentication
05/16/2007 13:06:35.477 Validating database connections using Windows Authentication
05/16/2007 13:06:35.868 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.337 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:36.352 Validating database connections using Windows Authentication
05/16/2007 13:06:36.680 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.696 User authentication was successful
05/16/2007 13:06:36.696 Stopping service: MSSQLServer
05/16/2007 13:06:38.711 Stopped service: MSSQLServer
05/16/2007 13:06:40.461 Authenticating user using Windows Authentication
05/16/2007 13:06:40.477 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:40.492 Starting service: MSSQLServer
05/16/2007 13:06:45.086 Started service: MSSQLServer
05/16/2007 13:06:45.101 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:45.523 Authenticating user using Windows Authentication
05/16/2007 13:06:45.539 Validating database connections using Windows Authentication
05/16/2007 13:06:46.085 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.414 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:46.429 Validating database connections using Windows Authentication
05/16/2007 13:06:46.742 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.757 User authentication was successful
05/16/2007 13:06:46.773 Stopping service: MSSQLServer
05/16/2007 13:06:48.788 Stopped service: MSSQLServer
05/16/2007 13:06:48.835 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.851 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.866 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:48.882 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.287 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.303 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.662 Locked file: Checking for locked files
05/16/2007 13:07:05.099 Attempting to pause the 32 bit ngen queue
05/16/2007 13:07:05.271 Installing product: SQL9
05/16/2007 13:07:05.286 Installing instance: MSSQLSERVER
05/16/2007 13:07:05.302 Installing target: DC-01
05/16/2007 13:07:05.317 Installing file: sqlrun_sql.msp
05/16/2007 13:07:05.349 Copy Engine: Creating MSP install log file at: C:ProgrammiMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
05/16/2007 13:07:05.364 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:07:05.380 Registry: Cannot read registry key value "Debug"
05/16/2007 13:09:06.458 MSP Error: 29506 Impossibile modificare le autorizzazioni di protezione del file C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLData per l'utente SYSTEM. Per continuare, verificare l'esistenza dell'account e del dominio che eseguono l'installazione di SQL Server. Verificare inoltre che tale account disponga dei privilegi di amministratore e che sia presente nell'unitĂ di destinazione.
05/16/2007 13:10:03.685 MSP returned 1603: Si è verificato un errore irreversibile durante l'installazione.
05/16/2007 13:10:03.701 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:10:03.716 Registry: Cannot read registry key value "Debug"
05/16/2007 13:10:04.248 Copy Engine: Error, unable to install MSP file: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLFilessqlrun_sql.msp
05/16/2007 13:10:04.310 The following exception occurred: Impossibile installare il file MSP di Windows Installer Date: 05/16/2007 13:10:04.310 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
05/16/2007 13:10:08.966 Watson: Param1 = Do_sqlFileSDDL
05/16/2007 13:10:08.997 Watson: Param2 = 0x7342
05/16/2007 13:10:09.044 Watson: Param3 = ExceptionInSDDL
05/16/2007 13:10:09.075 Watson: Param4 = 0x7342
05/16/2007 13:10:09.106 Watson: Param5 = sqlcasqlsddlca.cpp@65
05/16/2007 13:10:09.153 Watson: Param6 = Unknown
05/16/2007 13:10:09.184 Watson: Param7 = SQL9
05/16/2007 13:10:09.200 Watson: Param8 = Hotfix@
05/16/2007 13:10:09.231 Watson: Param9 = x86
05/16/2007 13:10:09.247 Watson: Param10 = 3042
05/16/2007 13:10:09.309 Installed product: SQL9
05/16/2007 13:10:09.356 Hotfix package completed
05/16/2007 13:10:09.388 Attempting to continue the 32 bit ngen queue
View 1 Replies
View Related
Oct 26, 2005
Hello,I am trying to connect to a SQL SERVER 2005 database. The database file is in App_Data folder under Inetpub/[AppRoot]Here's the Connection String:"Data Source=SERVER2/YUKON;AttachDbFilename=C:/Inetpub/MyNotes/App_Data/MyNotesDB.mdf;User ID=sa;Password=****"Every time I try to connect I get a this error on my page: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."Here's the stack trace:[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +684979 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +207 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +890 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +601 System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +159 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +346 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +445 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +304 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 MyNotes.Membership.MembershipManager.CreateMember(MemberProfile objMemberProfile) in c:InetpubMyNotesApp_CodeMyNotes.Membership.cs:21 _Default.Page_Load(Object sender, EventArgs e) in c:InetpubMyNotesDefault.aspx.cs:23 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +36 System.Web.UI.Control.OnLoad(EventArgs e) +102 System.Web.UI.Control.LoadRecursive() +47 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1064Thanks in advance,Arnie
View 1 Replies
View Related
Jul 25, 2007
Hello, How are you?
I have a problem when I try to create a new connection with Microsoft SQL Server 2005 Compact Edition from Visual Studio 2005 IDE. When I€™m going to choose the data source, the SQL Server 2005 Compact Edition provider doesn€™t appear in the list. I installed the SQL Server 2005 Compact Edition from this page http://www.microsoft.com/downloads/details.aspx?FamilyId=%2085E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&displaylang=en. In the additional information says by installing SQLServerCE31-EN.msi installs the provider (System.Data.SqlServerCe.dll) in the GAC (global assembly cache) and registers the OLEDB provider (sqlceoledb30.dll). So, I don€™t understand why couldn€™t I create a new connection with Microsoft SQL Server 2005 Compact Edition from Visual Studio 2005 IDE?
I appreciate your help€¦
View 6 Replies
View Related
