Linked Server Setup - SQL 2005 RTM
Jan 21, 2006
<<cross posted from microsoft.public.sqlserver.server>>
Environment: Windows 2003 Standard Edition SP1, SQL 2005 EE RTM (both
servers)
I am getting the following messages when I run this query:
select * from LINKEDSERVER.databasename.dbo.tablename
OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
message "An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow
remote connections.".
Msg 782, Level 16, State 1, Line 0
SQL Network Interfaces: No credentials are available in the security
package
OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
message "Client unable to establish connection".
Msg 782, Level 16, State 1, Line 0
SQL Network Interfaces: No credentials are available in the security
package
LINKEDSERVER is set up as a SQL Server linked server., with no login
mapping, and connections will be made using the login's current
security context.
Both servers allow local and remote connections via TCP/IP, and Named
Pipes is disabled on both servers. Both servers are trusted for
delegation, and the service accounts for the MSSQLSERVER service on
both servers are also trusted for delegation.
We are auditing successful and failed logins, and are not seeing any
activity on the linked server.
Any help would be appreciated.
Randy
View 3 Replies
ADVERTISEMENT
Feb 13, 2008
I am trying to set up a liked server using the UI in Management studio. In the Object Explorer I can see the server i want to link to MyServer2 and I have connected to it. I goto to the server in which i want to create the link MyServer1 and click on Server Objects then Linked Servers, New Linked Server.
In the server name I enter the server I want to link to, MyServer1. I don't know what to enter or where after that? What else do i need to set up?
When i try this select i get the following error.
select * from MyServer1.MyDB.dbo.MyTable
Error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "SQLNCLI" for linked server "MyServer1" reported an error. Authentication failed.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "MyServer1".
View 9 Replies
View Related
Nov 6, 2007
I'm trying to link my local SQL 2005 with a remote oracle database. I have downloaded the oracle 10g client. It seems the client installed a data source driver for me to use (Oracle in OraDb10g_home2). I created a new data source named 'Company' which I have successfully connecting using that driver.
The following is the script I'm using to create my linked server:
USE master
GO
sp_addlinkedserver
@server = 'Company',
@provider = 'OraOLEDB.Oracle',
@srvproduct = 'oracle',
@datasrc = 'Company'
GO
sp_addlinkedsrvlogin
@rmtsrvname = 'Company',
@useself = 'false',
@rmtuser = 'Company1',
@rmtpassword = 'MyPassword'
These both execute successfully.
Then when I go to make a select call:
SELECT * FROM OPENQUERY(Company, 'SELECT * FROM CAMPUS')
I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "Company" reported an error. The provider did not give any information about the error.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "Company".
I think my proplem may be that this provider does not match with my data source.... Any ideas?
View 2 Replies
View Related
Oct 1, 2007
I'm trying to add a linked server (sql 2005 9.00.1399.06) to a sql server 2005 instance (9.00.3042). I have chosen "login's current security context. All I can see are the system tables on the remote server. It seems to be using the "NT AUTHORITYANONYMOUS LOGON" account instead of my windows account because if I make it sysadmin I can see all of the databases on the server. Does anyone know why it is doing this and how to get it to use my windows account to make the connection?
View 15 Replies
View Related
Oct 26, 1999
I am having problems setting up a linked server in 7.0 Enterprise Manager. I am trying to setup the linked server using the "they will be imperonated" choice for the "For all users that are not defined in the list below" choice on the security tab. All servers I am trying to link to are registered in enterprise manager.
I can setup the linked servers on the source server itself and access tables from the linked servers as long as I am logged into the source server (where the linked servers are defined). E.G. I am logged into server SQL2 and have linked to server TST2. I can see tables from SQL2 in enterprise manager just fine.
However, when I try to access the linked server (TST2) from an enterprise manager running on an NT workstation (NT-RINEHARTS) or a 9x PC than I get the following error:
18456: Login failed for user ''.
It looks like the domain nameusername is not getting passed along to the linked server. Why won't this work from a remotely run Enterprise Manager? IS it supposed to? AM I leaving something out?
Again all linked servers are registered in Enetrprise Manager running on the NT workstation.
View 1 Replies
View Related
Mar 29, 2004
Been wandering around the searches and cannot find a specific answer so hopefully someone can help me. Basic situation is I'm setting up an automatic transfering of data to a historical database that resides on the same SQL Server.
exec sp_dropserver 'linked1', 'droplogins'
exec sp_addlinkedserver 'linked1', 'SQL Server'
exec sp_setnetname 'linked1', <Databasename>
exec sp_addlinkedsrvlogin 'linked1', 'false', null, <user>, <password>
SET ANSI_NULLS ON
go
SET ANSI_WARNINGS ON
go
select * from openquery (linked1, 'select * from dbo.table')
I run this and it says it cannot find the instance....
View 7 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 1 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 2 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 4 Replies
View Related
Oct 20, 2007
I just recently installed SQL Server 2005. I have a question about "SQL Server Management Studio".
I want my machine to act as the db server, so I can learn the basics of SQL Server 2005. Once I open
"SQL Server Management Studio" and attempt to connect to a database engine, I get the following error
Cannot connect to database engine....
I don't see any services running in the windows services console, I used to
work with SQL Server v7 awhile back and I remember within the left frame of "SQL Server Management Studio"
window, in the Registered Servers frame that the "Database Engine" icon usually had a green right arrow in it
when it was running correctly. Right now I have this "Database Engine" icon but there is a white circle with
no right green arrow signifying that it is running....
Thanks in advance for your help,
Wes
View 1 Replies
View Related
Dec 29, 2007
Hi Everyone,
I am using SQL Server 2005 with SQL Management Studio.
What I am trying to do is move tables and stored procedures from one database on one server to another database which is on a different server. Essentially, I am trying to move tables and stored procedures from a database on my local computer to a database on our staging server I was told the best way to do this would be to use a linked server. I have been trying to set one up using managment studio but right clicking on server-object and choosing 'new ---> Linked Server' but I have not been able to successfully create the connection.
Can anyone out there explain me to me how to setup the linked server using SQL 2005 Management Studio?
Thanks!
View 3 Replies
View Related
Apr 20, 2007
Hi all,
I'm new in this forum and id'like to post a strange error i can't solve by myself.
On a Win2003Server setted as a Stand Alone Server (without Active Directory) i installed my SQL SEERVER 2005 Workgroup edition with Management Studio and ODBC: Everything fine. a software house installed a IRP based on SQL Server: everything fine too.
They asked me to buil Dctive Directory on server. I should uninstall SQL Server, build up the AD domain and then reinstall SQL Server and from SQL Management Studio reconnect all the db.
Ok with uninstall operations, ok with AD setup but when i tryed to setup Sql Server 2005 it starts fine the DB engine but during management component setup i receive this error:
Tipo evento:Errore
Origine evento:MsiInstaller
Categoria evento:Nessuno
ID evento:11334
Data:20/04/2007
Ora:10.35.06
Utente:SERENAadministrator
Computer:SERVER
Descrizione:
Prodotto: Strumenti di Microsoft SQL Server 2005 -- Errore 1334. Impossibile installare il file "MS.AS.Oneclickcube.Resources.dll.53FCAAEE_2BA6_4556_896D_38710359E752". Impossibile trovare il file nel file CAB "Sql.cab". Questo può indicare un errore di rete, un errore di lettura dal CD-ROM o un problema con questo pacchetto.
Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico all'indirizzo http://go.microsoft.com/fwlink/events.asp.
Dati:
0000: 7b 36 41 44 31 32 42 45 {6AD12BE
0008: 35 2d 38 39 30 33 2d 34 5-8903-4
0010: 31 34 39 2d 41 32 44 42 149-A2DB
0018: 2d 30 46 41 32 39 31 31 -0FA2911
0020: 37 46 33 34 41 7d 7F34A}
sorry for Italian... hopes you can understand...
ideas? i notice that the IRP programmers setted up Visual Stuio 8 components on Server and on Analisys Components thers a OneClicCube.dll component...
On my CD there are no SQL.CAB archive...
no ideas at all..
Thanks a lot.
GAB
View 1 Replies
View Related
Oct 18, 2007
I just set it up on my laptop, its the express edition.
During setup I specified both auth (windows and login) and wrote down the username and password. I can connect through Management Studio with windows auth but not with the login.
I want to find the username and password. What do I need to do?
Thanks
View 3 Replies
View Related
Feb 1, 2006
Hello,(sorry for my English...)Could you help me please with installing SQL Servera 2005 ExpressEdition. I downloaded files:SQLEXPR.EXE - Microsoft SQL Server 2005 Express EditionSSEUtilSetup.EXE - SQL Server Express UtilitySqlServer2K5_BOL_Dec2005.msi - Books Online December 2005and I tried to run them sequentially. After installing SQLEXPR.EXEI had impression that I have little icons in Start menu (comparing tomy SQL Server 2000); I have a submenu:Microsoft SQL Server 2005 / Configuration ToolsSQL Server Configuration ManagerSQL Server Error and Usage ReportingSQL Server Surface Area ConfigurationI would like to have sth like Enterprise Manager (to see Northwinddatabase) and Query Analyzer (to query Northwind).So I decided to run SQLEXPR.EXE again: I see a report:System Configuration Check- WMI Service Requirement (Success)Messages* WMI Service Requirement* Check Passed- MSXML Requirement (Success)Messages* MSXML Requirement* Check Passed- Operating System Minimum Level Requirement (Success)Messages* Operating System Minimum Level Requirement* Check Passed- Operating System Service Pack Level Requirement. (Success)Messages* Operating System Service Pack Level Requirement.* Check Passed- SQL Server Edition Operating System Compatibility (Success)Messages* SQL Server Edition Operating System Compatibility* Check Passed- Minimum Hardware Requirement (Success)Messages* Minimum Hardware Requirement* Check Passed- Pending Reboot Requirement (Success)Messages* Pending Reboot Requirement* Check Passed- Default Installation Path Permission Requirement (Success)Messages* Default Installation Path Permission Requirement* Check Passed- Internet Explorer Requirement (Success)Messages* Internet Explorer Requirement* Check Passed- COM Plus Catalog Requirement (Success)Messages* COM Plus Catalog Requirement* Check Passed- ASP.Net Version Registration Requirement (Success)Messages* ASP.Net Version Registration Requirement* Check Passed- Minimum MDAC Version Requirement (Success)Messages* Minimum MDAC Version Requirement* Check Passed....and screen Feature Selection where I see Client Components notchecked. I decided to mark these components:Client Components "Will be installed on local hard drive"Connectivitiy Compenents "Will be installed on local hard drive"Software Development Kit "Will be installed on local hard drive"(I have free disk space); then I pressed "Next":Named instance: SQLExpressand "Next" again: on screen Existing compenents I see popup with amessage:"None of selected features can be installed or upgraded. Setup cannotproceed since no effective change is being made to the machine. (...)"but I had marked Client Components!Could you explain me please what I am doing wrong?Thank you very much for your help!(MP)
View 2 Replies
View Related
Nov 6, 2007
hi,
Whenever i tried to install Sql Server 2005, the installation fails giving errors for
event logs and error logs
[microsoft][SQL Native Client][SQL Server]. The server could not load DCOM...
In the log file,
Property(S): Ver.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90
Property(S): SqlTools.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90Tools
Property(S): checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C = **********
Property(S): SqlInstance.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceRegKey.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = Microsoft SQL ServerMSSQL.1
Property(S): InstanceName.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = SQLEXPRESS
Property(S): PackagecodeChanging = 1
Property(S): SqlInstance.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceInstall.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): SqlInstanceInstallDel.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): ProductState = -1
Property(S): TRANSFORMS = qlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): PackageCode = {A81ED606-6AF4-48DA-A5D9-1AFCC4767FEE}
Property(S): SqlInstance.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): MsiLogFileLocation = C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_SHITAL-PC_SQL.log
Property(S): Shared.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlToolsBinRes.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlToolsBinRes1033.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlInstance.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): SqlInstanceJet.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceOther.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): sqlevn70.rll.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033sqlevn70.rll
Property(S): Shared.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlSharedRes.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlSharedRes1033.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlVerComBin.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90
Property(S): InstanceName.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = SQLEXPRESS
Property(S): SqlInstance.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceName.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = SQLEXPRESS
Property(S): DataInstance.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceBackup.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup
Property(S): DataInstanceLog.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG
Property(S): DataInstanceTemplate.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): AdministratorsGroupQuoted = BUILTINAdministrators
Property(S): LocalSystemAccountQuoted = NT AUTHORITYSYSTEM
Property(S): QuotedServiceGroupSQL.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = SHITAL-PCSQLServer2005MSSQLUser$SHITAL-PC$SQLEXPRESS
Property(S): AdministratorsGroup = BUILTINAdministrators
Property(S): UsersGroupQuoted = BUILTINUsers
Property(S): UsersGroup = BUILTINUsers
Property(S): InstanceRegKey.BA9A7592_6647_4283_9B99_2885BD96A224 = Microsoft SQL ServerMSSQL.1
Property(S): DataInstance.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceTemplate.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): ModuleID_SYSDB2 = 75D79626_87FB_4E9A_B07F_87DAE18D0F36
Property(S): SqlInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): Data.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): DataInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): DataInstanceRepldata.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
epldata
Property(S): DataInstanceTxt.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlVerComBin.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90
Property(S): TempFolder = c:UsersshitalAppDataLocalTemp
Property(S): DataInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlInstanceBin.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): DataInstanceTxt.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): WORKINGDIRECTORY.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLREPLDATA
Property(S): InstanceRegKey.2F9C839A_286D_4B39_BD89_4DF4067604DF = Microsoft SQL ServerMSSQL.1
Property(S): SqlVerComBin.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90
Property(S): MSVSPrivateAssembliesEN.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COMen
Property(S): SqlVerComBin.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90
Property(S): WindowsFolder = c:Windows
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon Files
Property(S): MSShared.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft Shared
Property(S): DatabaseRepl.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase Replication
Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources1033
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources1033
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = c:2aae5517aa4b91d8f50a9cSetup
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {0D7C3EF4-D4A8-4796-9452-44FC73491B48}
Property(S): ProductToBeRegistered = 1
MSI (s) (24:44) [12:45:07:442]: Note: 1: 1708
MSI (s) (24:44) [12:45:07:442]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.
MSI (s) (24:44) [12:45:07:443]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.2.3042.00. Product Language: 1033. Installation success or error status: 1603.
MSI (s) (24:44) [12:45:07:457]: Cleaning up uninstalled install packages, if any exist
MSI (s) (24:44) [12:45:07:457]: MainEngineThread is returning 1603
MSI (s) (24:BC) [12:45:07:458]: Destroying RemoteAPI object.
MSI (s) (24:74) [12:45:07:459]: Custom Action Manager thread ending.
MSI (s) (24:BC) [12:45:07:460]: RESTART MANAGER: Session closed.
MSI (s) (24:BC) [12:45:07:460]: No System Restore sequence number for this installation.
=== Logging stopped: 11/6/2007 12:45:07 ===
MSI (c) (F0:98) [12:45:07:514]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:98) [12:45:07:516]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/6/2007 12:45:07 ===
Can anyone provide me solution?
View 3 Replies
View Related
Jan 20, 2006
Hi,
Trying to install 64-bit SQL Server 2005 RTM on Windows 2003 x64 Server with SP 1. The Reporting services option is not enabled in the installation steps. The installation process gets completed without any errors, but the Reporting Services is not installed.
The server has IIS installed, the .NET framework 2.0 is installed by SQL Server 2005 RTM itself. Am I doing anything wrong.
Can anyone help/suggest ?
Thanks in advance.
View 5 Replies
View Related
Sep 14, 2007
"Setup failed" error when the installation auto-setups "Workstation Components, Books Online and Developement Tools" . It showed "MainEngineThread is returning 21 The device is not ready" in the log. Could not find a solution online. So I have to seek help here.
Here is the log:
=== Verbose logging started: 9/14/2007 17:29:16 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (8C:EC) [17:29:16:421]: Resetting cached policy values
MSI (c) (8C:EC) [17:29:16:421]: Machine policy value 'Debug' is 0
MSI (c) (8C:EC) [17:29:16:421]: ******* RunEngine:
******* Product: G:SQL Server x86ToolsSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (c) (8C:EC) [17:29:16:421]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (8C:EC) [17:29:16:421]: Grabbed execution mutex.
MSI (c) (8C:EC) [17:29:16:437]: Cloaking enabled.
MSI (c) (8C:EC) [17:29:16:437]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (8C:EC) [17:29:16:437]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:78) [17:29:16:437]: Grabbed execution mutex.
MSI (s) (30:FC) [17:29:16:437]: Resetting cached policy values
MSI (s) (30:FC) [17:29:16:437]: Machine policy value 'Debug' is 0
MSI (s) (30:FC) [17:29:16:437]: ******* RunEngine:
******* Product: G:SQL Server x86ToolsSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (s) (30:FC) [17:29:16:437]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (30:FC) [17:29:16:453]: File will have security applied from OpCode.
MSI (s) (30:FC) [17:30:22:078]: Note: 1: 2382
MSI (s) (30:FC) [17:30:29:890]: MainEngineThread is returning 21
The device is not ready.
MSI (c) (8C:EC) [17:30:29:890]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:EC) [17:30:29:890]: MainEngineThread is returning 21
=== Verbose logging stopped: 9/14/2007 17:30:29 ===
I removed the SQL 2005 Express then started installing the Client Components in 2005 developer version. I tried to install into C drive or another drive but got the same error.
Anyone knows anything about it?
Many thanks.
View 1 Replies
View Related
Oct 12, 2006
I installed 2005 Developer edition on a local workstation in our lab. I can connect to a network SQL Server with it just fine. But I do not have a local instance of SQL Server on this workstation.
How do I create a local instance of SQL Server? (box is WinXPPro-SP3)
After accepting the defaults for this installation, I noticed that there were no "local" instances of SQL server available, whereby I could go out and create my own test databases locally or copy a few tables from a production server over to my local box for testing. I'm looking through the books online and do not see (maybe I missed it) the steps to creating a local instance for setting up a workstaiton as a 'test' environment.
Assistance is appreciated.
RLN
View 4 Replies
View Related
Oct 8, 2006
hi..
I am getting the following error while installing SQL Server 2005 Eval edition on Win XP.
I am the administrator on the system.
Error:
SQL server Setup was unable to add user NT AUTHORITYSYSTEM to local group SQLSERVER2005MSFTEUSER$COMPUTERNAME$INSTANCENAME.
View 1 Replies
View Related
Oct 24, 2007
Hello all,
I have tried to install SQL Server 2005 Standard edition with CLUSTERING. I faced a problem and everything rolls back.
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup was unable add user domain1xyz to local group domain1IT Security Admin-Group.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29512&EvtType=sqlca%5csqlsecurityca.cpp%40Do_sqlGroupMember%40Do_sqlGroupMember%40x6ba
I have refered to PostI=1659185 posted by Fly and it still won't be able to fix my problem.
I have added LOCAL SERVICE into the local group (SQLServer2005MSFTEUser$AAA$MSSQLSERVER), but it still can't work.
Please can someone help me on this. Thank a lot....
View 6 Replies
View Related
Mar 26, 2007
I run setup using GUI. It upgrades all components of the existing installation w/out any problems except the last component. That is, it proceeds with the installation of SQL Server Database Serices and at the end fails to shut down the SQL Server and aborts the installation reporting the following:
"Service 'Computer_NameSQLEXPRESS' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386)".
I am running Windows XP SP2 with both .NET 2.0 and .NET 3.0 installed on it. I am logged in as a system administrator.
The most puzzling to me things are:
- the setup starts AND STOPS w/out any problems SQL Server Reporting Services and SQL Server VSS Writer (thus finding enough privileges for both).
- the setup starts the SQL Server w/out any problems (thus it finds enough privileges to START A SYSTEM SERVICE) and then fails as described above 'lucking privileges".
During installation before failing the setup displays following:
"Run as Normal User. RANU instance Shutdwon in progress: MSSQL$SQLEXPRESS". The "normal user" puzzles me too, unless the SQL Server itself is meant here.
Any suggestions would be appreciated. I can provide the installation log file as well.
Thanks.
View 5 Replies
View Related
Apr 21, 2008
Hi,
Is it possible to install SQL Server 2005 Eval on a Virtual PC 2007
client running Server 2008 Beta? Nothing says it isn't possible, it
says I need to service pack it right away, but before it gets started
it comes up with the error 'sqlcu.dll failed to load'. Anyone know
what this is all about?
Any ideas?
Any help would be appreciated.
Thanks!
View 1 Replies
View Related
Aug 17, 2006
Hello Experts,
I have been unable to install SQL Express 2005 Server on my Windows 2003 Server (with SP2 installed). I keep getting an error message saying that Microsoft Windows Installer 3.1 is not installed.
Click here for image
So, I downloaded Microsoft Windows Installer 3.1 v2 (WindowsInstaller-KB893803-v2-x86.exe) but whenever I try to install it I get an error message saying that "the Service Pack version of this system is newer than the update you are applying" and that there is no need to install the update and it stops there.
Click here for image
Is there a workaround to this? How can I get Microsoft Windows Installer 3.1 installed? I tried going to the Windows Update site, I already have everything installed and I even started the Windows Installer service manually. Has anyone else experienced this?
How can I get SQL Server 2005 Express installed if not how can I install SQL Server 2000 on tihs machine? The only reason I am trying to install SQL Server 2005 is because wanted to try it so I uninstalled SQL Server 2000 now I can no longer install SQL Server 2000 again because it won't let me because of the SP2 patch.
Help! :(
View 1 Replies
View Related
Dec 2, 2006
Hi All,
Is anyone can show me how to setup sql server to do backup daily automatically?
TIA
View 2 Replies
View Related
Oct 11, 2007
Ive been trying to get some type of Blogpost tutorial Etc on how to set up SQL Server 2005 to serve data to a website1 How do I setup users? a) Can I have 3 roles? 1a) Owner of DB can read/write 2a) reader Can Only read from database 3a) Writer. Can only write to database How would I set this up? How can I call all these from ASP.NET depending on what the user is currently using on the website? eg: Just serving pages with content (reader) Forms (writter) admin (owner)I also need to have the SQL keep sessions (Ive already ran aspnet_reqSQL.exe) and created all that im just unsure what type user can access all thisAny tutorials on how to set up a whole WEb application project from DB to VS 2005? Thanks
View 3 Replies
View Related
Aug 24, 2005
Hi
I need help when i try to install Microsoft SQL Server 2005 CTP Setup it fails every time i tried and now i don't what to do
Thank's
View 2 Replies
View Related
Aug 18, 2007
Hi,
My name is Vinh, I am a new bee in SQL Server 2005. I am using template script (see below) from SQL Server to create account but when I am right click in database mail for testing email and I got the message, could not connect to mail server.
Below I am trying to use smtp to connect but I know in my company we are using Exchange Mail Server. will that make a lot different?
Please help me,
Thank you very much,
sp_configure 'database mail xps', 1
GO
reconfigure
GO
-------------------------------------------------------------
-- Database Mail Simple Configuration Template.
--
-- This template creates a Database Mail profile, an SMTP account and
-- associates the account to the profile.
-- The template does not grant access to the new profile for
-- any database principals. Use msdb.dbo.sysmail_add_principalprofile
-- to grant access to the new profile for users who are not
-- members of sysadmin.
-------------------------------------------------------------
DECLARE @profile_name sysname,
@account_name sysname,
@SMTP_servername sysname,
@email_address NVARCHAR(128),
@display_name NVARCHAR(128);
-- Profile name. Replace with the name for your profile
SET @profile_name = 'TestProfile';
-- Account information. Replace with the information for your account.
SET @account_name = 'vdang';
SET @SMTP_servername = 'smtp.cgdnow.com';
SET @email_address = 'vdang@cdgnow.com';
SET @display_name = 'Vinh, Dang';
-- Verify the specified account and profile do not already exist.
IF EXISTS (SELECT * FROM msdb.dbo.sysmail_profile WHERE name = @profile_name)
BEGIN
RAISERROR('The specified Database Mail profile (<profile_name,sysname,SampleProfile>) already exists.', 16, 1);
GOTO done;
END;
IF EXISTS (SELECT * FROM msdb.dbo.sysmail_account WHERE name = @account_name )
BEGIN
RAISERROR('The specified Database Mail account (<account_name,sysname,SampleAccount>) already exists.', 16, 1) ;
GOTO done;
END;
-- Start a transaction before adding the account and the profile
BEGIN TRANSACTION ;
DECLARE @rv INT;
-- Add the account
EXECUTE @rv=msdb.dbo.sysmail_add_account_sp
@account_name = @account_name,
@email_address = @email_address,
@display_name = @display_name,
@mailserver_name = @SMTP_servername;
IF @rv<>0
BEGIN
RAISERROR('Failed to create the specified Database Mail account (<account_name,sysname,SampleAccount>).', 16, 1) ;
GOTO done;
END
-- Add the profile
EXECUTE @rv=msdb.dbo.sysmail_add_profile_sp
@profile_name = @profile_name ;
IF @rv<>0
BEGIN
RAISERROR('Failed to create the specified Database Mail profile (<profile_name,sysname,SampleProfile>).', 16, 1);
ROLLBACK TRANSACTION;
GOTO done;
END;
-- Associate the account with the profile.
EXECUTE @rv=msdb.dbo.sysmail_add_profileaccount_sp
@profile_name = @profile_name,
@account_name = @account_name,
@sequence_number = 1 ;
IF @rv<>0
BEGIN
RAISERROR('Failed to associate the speficied profile with the specified account (<account_name,sysname,SampleAccount>).', 16, 1) ;
ROLLBACK TRANSACTION;
GOTO done;
END;
COMMIT TRANSACTION;
done:
GO
View 3 Replies
View Related
Jul 17, 2007
I am facing a problem while installing Sql server 2005 Developer edition on Windows XP Professional SP 2 , It says Cannot install native client use correct SQLCLNI.msi file and Native client installation fails also the set up for client tools fails.
Any help will be greatly appreciated.
Pankaj Joshi
View 1 Replies
View Related
Mar 10, 2006
Trying to install SQL Server 2005 Standard on a pc with Windows xp pro spII with Visual Studio 2005 pro installed.I receive an error after 2/3 of the setup time.This is the error: Linkid: 20476Product name Microsoft SQL ServerProduct version 9.00.1399.06Message source Setup.rllMessage id 50000EvtType packageengineinstallpackageaction
View 10 Replies
View Related
May 1, 2006
Hi I am trying to learn VB 2005 and I am reaching a step in my studies which requires downloading Sql Server 2005. However every time I attempt to download, I receive this error message.
"SQL Server Setup cannot install files to the compressed or encrypted folder: c:Program FilesMicrosoft SQL Server. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again."
I have tried saving it to another folder, this did not help. Somewhere in my search for answers, I came across something that said I needed a strong Sa authentication or password. I did not have a place to store a password in the setup program and when I went to administration password all my fields were blank, so it should not have needed any password. I also tried the link that this error message directed me to and they said they had no further information on this error.
I have exhausted all the leads, a beginner could possibly come across, except you. Please Help!
View 7 Replies
View Related
Jan 7, 2008
"SQL Server is unable to run. Either the owning node or all nodes that currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online."
Can someone tell me what's the cause of this error?
How can this be corrected?
I am very grateful for all feedback.
View 1 Replies
View Related
Mar 28, 2007
i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190
------------------------------
BUTTONS:
OK
------------------------------
View 3 Replies
View Related
Apr 16, 2007
Hi
I would like to know, if it is at all possible for Setup files of SQL Server 2005 to be distributed. We have clients who currently use our software which makes use SQL Server 2000. We are looking ahead at distributing our new version with SQL Server 2005 and would like create an Installation package that will upgrade the database engine to the Workgroup or Enterprise editions of SQL Server 2005. Are there any suggestions around this topic, we are looking at ways in making this task of upgrading the engine as streamlined and automated for our Client. Please include advise with regards to licensing.
cheers
Kevin
View 1 Replies
View Related