Hello,
I have a server with both SQL 2008 and SQL 2008 R2 and am in the process to update the 2008 R2 version.
So my question is as follows:
If I upgrade 2008 R2 to the newest version does this interrupt connectivity to the 2008 instance? Or is the 2008 always available through out the process fo upgrading 2008 R2?
Regards
Paul
unhandled exception has occured in your application . if u click continue the application will ignore and attempt to continue.
an error occurred creating the configuration section handler for usersettings/microsoft.sqlserver.configuration.landingpage.properties.Settings:could not load file or assembly System,version=4.0.0.0 culture=neutral,public key token=????????????
See the end of this message for details on invokingHi all,
I Uninstalled SQL Server 2012 from control panel after uninstallation I found few folders on C:Program files so I manually deleted the SQL folders over there and rebooted the server.
Now i'm not unable to Install new SQL on this server, the following page suddenly flashes out(sudden disappear) . Could any one help me how to troubleshoot this issue and allow me to install on this server.
Please respond this as per my urgency!
Thanks all.
DBA
Hi Team,
We have SQL Server 2005 Standard Edition ( 64 bit ) with SP3 , GDR(4053) and Hotfix 1546.
SQL Build version - 9.0.4053
Before applying SQL Service Pack (SP4), executed the FindSQLInstalls.vbs to find the missing msi and msp file.
Fixed most of them from earlier Service Pack (SP3) and GDR, but output also show the below hotfix 1546 which isunavailable in microsoft portal.
Display Name: Hotfix 1546 for SQL Server Database Services 2005 (64-bit) ENU (KB919357)
KB Article URL: ;http://support.microsoft.com/?kbid=919357
Can someone suggest about the above hotfix and provide if any other alternate URL available for the same.
Thanks,
Dathuraj Pasarge
Dathuraj
My company intend to buy a new server and will dedicate that for SQL Server which will serve an in-house developed application.
How can we know how many processors are enough to buy?
I know that each SQL Server edition and version has it's different limitation of the number of processors it can support, for example SQL Server 2012 Standard Edition can support up to 4 sockets or 16 cores per SQL Server Instance, but this does not mean that I have to buy 4 physical CPUs. two could be enough. how can I know?
Hi,
I am the happy owner of a SQL express 2008 R2 holding my DB.
I have my DB primary data file at 7 GB
In DB properties, I have initial size of primary db at 7022 MB, autogrowth = by 1 MB, unlimited.
I query table sizes with :
select object_name(id) [Table Name],
[Table Size] = convert (varchar, dpages * 8 / 1024) + 'MB'
from sysindexes where indid in (0,1)
order by dpages desc
total size of all my tables is then 1171 MB
I do shrink / files / file type = data => available free space is 0.25 MB
I'm afraid it will hit the 10 GB size.
How do I reduce the DB size ? it is possible to change the initial size of primary db ?
thanks
I received the above error reinstalling SQL Server 2008. I have tried all suggestions. This error also appears when I install any version of SQL Server.
I have also installed;
Microsoft® .NET Framework Version 2.0.50727.4927
Microsoft® .NET Framework Version 4.0.31106.0
Microsoft® .NET Framework Version 3.0.6920.50
Microsoft Visual C++ 2005 Redistributable (x64) 8.0.59192
Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
Microsoft Visual C++ 2010 x64 Redistributable 10.0.40219
Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -2068052081
Exit facility code: 1212
Exit error code: 1935
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time: 2014-02-23 19:17:20
End time: 2014-02-23 19:21:35
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SqlSupport_KatmaiRTM_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: OHPC
Machine processor count: 2
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: H:\SQLServer2008R2_SP1\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: OHPC\Robert
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SystemConfigurationCheck_Report.htm
SFC/ Scannow
2014-02-23 19:08:22, Info CSI 0000016f [SR] Verifying 100 (0x0000000000000064) components
2014-02-23 19:08:22, Info CSI 00000170 [SR] Beginning Verify and Repair transaction
2014-02-23 19:08:23, Info CSI 00000172 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:23, Info CSI 00000174 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:26, Info CSI 00000176 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:26, Info CSI 00000177 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2014-02-23 19:08:26, Info CSI 00000179 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
source file in store is also corrupted
2014-02-23 19:08:27, Info CSI 0000017c [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:27, Info CSI 0000017d [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
2014-02-23 19:08:27, Info CSI 00000180 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
source file in store is also corrupted
2014-02-23 19:08:27, Info CSI 00000182 [SR] Verify complete
2014-02-23 19:12:33, Info CSI 00000326 [SR] Verifying 100 (0x0000000000000064) components
2014-02-23 19:12:33, Info CSI 00000327 [SR] Beginning Verify and Repair transaction
2014-02-23 19:12:33, Info CSI 00000329 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:12:35, Info CSI 0000032b [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:12:35, Info CSI 0000032c [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
2014-02-23 19:12:35, Info CSI 0000032f [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
source file in store is also corrupted
2014-02-23 19:12:36, Info CSI 00000331 [SR] Verify complete
2014-02-23 19:13:14, Info CSI 0000035d [SR] Repairing 3 components
2014-02-23 19:13:14, Info CSI 0000035e [SR] Beginning Verify and Repair transaction
2014-02-23 19:13:14, Info CSI 00000360 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info CSI 00000362 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info CSI 00000364 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info CSI 00000366 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info CSI 00000367 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
2014-02-23 19:13:15, Info CSI 0000036a [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
source file in store is also corrupted
2014-02-23 19:13:15, Info CSI 0000036c [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:15, Info CSI 0000036d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2014-02-23 19:13:15, Info CSI 0000036f [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
source file in store is also corrupted
2014-02-23 19:13:15, Info CSI 00000371 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:15, Info CSI 00000372 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
2014-02-23 19:13:15, Info CSI 00000375 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
source file in store is also corrupted
2014-02-23 19:13:15, Info CSI 00000377 [SR] Repair complete
2014-02-23 19:13:15, Info CSI 00000378 [SR] Committing transaction
2014-02-23 19:13:15, Info CSI 0000037c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired
Hi All,
We recently migrated Sql 2000 DB to Sql 2012. Now, the client is asking compatibility report to check and confirm we are not using any deprecated features from SQL Server 2000 into SQL Server 2012.
While, we did installed the Upgrade Advisor & started to give the server / fully qualified domain name, we are getting below error.
TITLE: Detect SQL Server Components
------------------------------
Upgrade Advisor could not detect SQL Server components on the server. Please check if current user has the privilege to access target server's registry, and if the Remote Registry service in target server is started.
------------------------------
ADDITIONAL INFORMATION:
Requested registry access is not allowed. (mscorlib)
Kindly provide with your inputs.
Thanks & Regards, VSVaidya
Hello,
I installed SQL with DB engine and Reporting Services for SCOM2012R2. Before installation I created in the AD group called SQLAdmins, service accounts and added these accounts to this group and account for myself. During setup I added this group to administrators. Setup finished, also I installed SCOM reporting and reports are visible in the SCOM console. But when I open SQL Management Studio in the Security - Logins I see only this group and disabled sa. Group has only public role. I am not pro SQL admin, could you please help what to do and what is wrong? Just in case I checked my another SCOM environment (test lab) with reporting, a group which was added to admins during setup has sysadmin role and also I see additional logins for accounts from this group. Also one addition, the account which was used to install SQL was added to the group in the AD by AD admin during SQL installation, but account has domain admin privileges.
I am running SQL server 2008 R2, 64 bit, When i attempt to backup Blackbaud Financial Edge version 7.86 either manaully or via a scheudle, I am SUDDENLY getting error 'Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). NOTE: The step was retried the requested number of times (1) without succeeding. The step failed.'
A Blackbaud Article (BB584984) says to install the SQL Server 2005 Backward Compatibility components. What concerns me is why this broke suddenly and why the components would fix it, as I am wary of changing something without knowing why the fix should work, especially after it worked without the components for years. Blackbaud will not support this part of my question, as they disclaim all support for SQL.
Any help would be appreciated.
Hello,
During installations, I got the following error:
1)
Microsoft.SqlServer.Configuration.Sco.DirectoryAttributesMissmatch: Folder C:\Program Files\Microsoft SQL Server has an unsupported attribute (Compressed) set. Please resolve this issue by removing the unsupported attribute from the folder using folder properties dialog.
2)
Microsoft.SqlServer.Configuration.SetupExtension.CompressedDirException: The specified directory, "C:\Program Files\Microsoft SQL Server\", for the INSTALLSHAREDDIR parameter is not valid because this directory is compressed or is in a compressed directory. Specify a directory that is not compressed.
3)
Microsoft.SqlServer.Configuration.SetupExtension.CompressedDirException: The specified directory, "C:\Program Files (x86)\Microsoft SQL Server\", for the INSTALLSHAREDWOWDIR parameter is not valid because this directory is compressed or is in a compressed directory. Specify a directory that is not compressed.
Can you help with these errors?
Hi,
I’ve been upgrading several of my clients and ran into this problem for one of them.
When doing the upgrade I got..
Looking at the error logs indicated..
2015-03-21 11:54:07.58 spid7s Database 'master' is upgrading script 'provisionsystemaccounts.sql' from level 0 to level 2.
2015-03-21 11:54:07.59 spid7s ----------------------------------------
2015-03-21 11:54:07.59 spid7s Starting provisionsystemaccounts.sql ...
2015-03-21 11:54:07.59 spid7s ----------------------------------------
2015-03-21 11:54:08.02 spid7s Error: 15151, Severity: 16, State: 1.
2015-03-21 11:54:08.02 spid7s Cannot find the user 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', because it does not exist or you do not have permission.
2015-03-21 11:54:08.03 spid7s Error: 912, Severity: 21, State: 2.
2015-03-21 11:54:08.03 spid7s Script level upgrade for database 'master' failed because upgrade step 'provisionsystemaccounts.sql' encountered error 15151, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2015-03-21 11:54:08.03 spid7s Error: 3417, Severity: 21, State: 3.
2015-03-21 11:54:08.03 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2015-03-21 11:54:08.03 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Running the Repair from the Installation centre brings up the same error.
I noticed that the instance appears to be upgraded but basically the service won’t run. I can start it but it just stops again.
So I found this which seems the same as my problem..
https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/
Even though I can start the SQL Services using point 1 from the link above I can’t connect to sql using DAC.
The sqlcmd won’t work and trying to connect through SSMS.
> SQLCMD –E –A. I’ve also tried >SQLCMD FILESERVER1\ORSQLEXP –E –A and get the same results
HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port.
Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].
When I try to connect to DAC via SSMS I get ..
So I seem to currently have 2 problems, one using sqlcmd/DAC and the other with provisionsystemaccounts.sql.
The sqlbrowser is running but from 90 (not sure if that matters) and I have removed (following online research) the 80 and 90 binn settings from the PATH just leaving 100 but this hasn’t changed the errors.
I’ve tried enabling DAC using this advice below but it hasn’t made any difference. The service keeps stopping and no SQLCMD action.
So after trying numerous options I currently stumped.
:)
R/s Sir/Madam,
I am the student of MCA & created a project based on LAN using vb.net & SQL SERVER 2008 R2 withOnlineExam named instance having password as abc@123.com. while I am creating a setup using .Net setup & deployment (VS2010) it installs prerequisites from installation folder but does not create a named instance as I mentioned.
My problem is that I just want to install SQL SERVER 2008 R2 with named instance but without users interaction. I already tried it from command line(cmd) and even using configuration.ini files, but the problem persists...
Please, help to make me such things...I request you to help me out of this....please....
Thanks in advance.
Amol Gaikawad,
I got a sql 2012 always on setup between 2 standalone servers in 2 different locations.
I do not understand why I need cluster manager managing the 2 nodes.
I have cluster manager but there is no shared disks. there are 2 nodes under cluster manager and one cluster name.
what would be the different between the cluster name here and the availability group listener name in sql 2012? they are both different names
I am trying to install Remote Blob Storage in Sharepoint Server 2013 with SQL Server 2008 R2 Express, but it is not creating the table in the database.
Here is my script
msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content_Blob_001" DBINSTANCE="SHAREPOINT" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
APPCOMPAT: looking for appcompat database entry with ProductCode '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}
My SQL server version is 10.50.6000.34
In the log file I found the following lines in the bottom of the file, but the table is not in the content database.
Product: SQL Server 2008 R2 Remote Blob Store -- Configuration completed successfully.
I am struggling with this issue for long. It would be great if someone could help.
=== Verbose logging started: 3/4/2015 15:27:16 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (E4:A4) [15:27:16:166]: Resetting cached policy values
MSI (c) (E4:A4) [15:27:16:166]: Machine policy value 'Debug' is 0
MSI (c) (E4:A4) [15:27:16:166]: ******* RunEngine:
******* Product: RBS.msi
******* Action:
******* CommandLine: **********
MSI (c) (E4:A4) [15:27:16:166]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E4:A4) [15:27:16:166]: Grabbed execution mutex.
MSI (c) (E4:A4) [15:27:16:182]: Cloaking enabled.
MSI (c) (E4:A4) [15:27:16:182]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E4:A4) [15:27:16:182]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:94) [15:27:16:182]: Running installation inside multi-package transaction D:\RBS.msi
MSI (s) (00:94) [15:27:16:182]: Grabbed execution mutex.
MSI (s) (00:54) [15:27:16:182]: Resetting cached policy values
MSI (s) (00:54) [15:27:16:182]: Machine policy value 'Debug' is 0
MSI (s) (00:54) [15:27:16:182]: ******* RunEngine:
******* Product: D:\RBS.msi
******* Action:
******* CommandLine: **********
MSI (s) (00:54) [15:27:16:197]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (00:54) [15:27:16:197]: Setting cached product context: User non-assigned for product: FB42F99F09B0E3646985F32DFE3C9C29
MSI (s) (00:54) [15:27:16:197]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:197]: SRSetRestorePoint skipped for this transaction.
MSI (s) (00:54) [15:27:16:197]: End dialog not enabled
MSI (s) (00:54) [15:27:16:197]: Original package ==> D:\RBS.msi
MSI (s) (00:54) [15:27:16:197]: Package we're running from ==> C:\Windows\Installer\6847f.msi
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: looking for appcompat database entry with ProductCode '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: MSCOREE not loaded loading copy from system32
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisablePatch' is 0
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (00:54) [15:27:16:213]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: looking for appcompat database entry with ProductCode '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (00:54) [15:27:16:213]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (00:54) [15:27:16:213]: Transforms are not secure.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\rbs_install_log.txt'.
MSI (s) (00:54) [15:27:16:213]: Command Line: TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=WSS_Content_Blob_001 DBINSTANCE=SHAREPOINT FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 CURRENTDIRECTORY=D:\ CLIENTUILEVEL=3 CLIENTPROCESSID=10980
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{1AC68E73-94F1-4A01-B229-82B2F73C3326}'.
MSI (s) (00:54) [15:27:16:213]: Product Code passed to Engine.Initialize: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (00:54) [15:27:16:213]: Product Code from property table before transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (00:54) [15:27:16:213]: Product Code from property table after transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (00:54) [15:27:16:213]: Product registered: entering maintenance mode
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (00:54) [15:27:16:213]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (00:54) [15:27:16:213]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Specifed source is already in a list.
MSI (s) (00:54) [15:27:16:213]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisableBrowse' is 0
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (00:54) [15:27:16:213]: Adding new sources is allowed.
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Package name retrieved from configuration data: 'RBS.msi'
MSI (s) (00:54) [15:27:16:213]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisableMsi' is 1
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (00:54) [15:27:16:213]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (00:54) [15:27:16:213]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (00:54) [15:27:16:213]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (00:54) [15:27:16:213]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (00:54) [15:27:16:213]: Running product '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}' with elevated privileges: Product is assigned.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding TRUSTSERVERCERTIFICATE property. Its value is 'true'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Modifying FILEGROUP property. Its current value is 'default'. Its new value: 'PRIMARY'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding DBNAME property. Its value is 'WSS_Content_Blob_001'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding DBINSTANCE property. Its value is 'SHAREPOINT'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Modifying FILESTREAMFILEGROUP property. Its current value is 'default'. Its new value: 'RBSFilestreamProvider'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding FILESTREAMSTORENAME property. Its value is 'FilestreamProvider_1'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '10980'.
MSI (s) (00:54) [15:27:16:213]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is 'f13e91ecbfc5d34cae7163e948e320cc'.
MSI (s) (00:54) [15:27:16:213]: RESTART MANAGER: Session opened.
MSI (s) (00:54) [15:27:16:213]: TRANSFORMS property is now:
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (00:54) [15:27:16:213]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (00:54) [15:27:16:213]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming
MSI (s) (00:54) [15:27:16:213]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Favorites
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Documents
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Local
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Pictures
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (00:54) [15:27:16:229]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Desktop
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (00:54) [15:27:16:244]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
Property(S): PhysicalMemory = 8192
Property(S): VirtualMemory = 7158
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = medsvradmin
Property(S): UserSID = S-1-5-21-300911508-3398273753-3262312657-1000
Property(S): UserLanguageID = 1033
Property(S): ComputerName = JPNTKYINT01
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 15:27:21
Property(S): Date = 3/4/2015
Property(S): MsiNetAssemblySupport = 4.0.30319.34209
Property(S): MsiWin32AssemblySupport = 6.1.7601.17514
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): DATABASE = C:\Windows\Installer\6847f.msi
Property(S): OriginalDatabase = D:\RBS.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): ROOTDRIVE = D:\
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): DOTNETCOREPATH = 1
Property(S): SourcedirProduct = {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
Property(S): SOURCEDIR = D:\
MSI (s) (00:54) [15:27:21:049]: Note: 1: 1728
MSI (s) (00:54) [15:27:21:049]: Product: SQL Server 2008 R2 Remote Blob Store -- Configuration completed successfully.
MSI (s) (00:54) [15:27:21:049]: Windows Installer reconfigured the product. Product Name: SQL Server 2008 R2 Remote Blob Store. Product Version: 10.50.1600.1. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (00:54) [15:27:21:049]: Deferring clean up of packages/files, if any exist
MSI (s) (00:54) [15:27:21:049]: MainEngineThread is returning 0
MSI (s) (00:94) [15:27:21:049]: RESTART MANAGER: Session closed.
MSI (s) (00:94) [15:27:21:049]: No System Restore sequence number for this installation.
=== Logging stopped: 3/4/2015 15:27:21 ===
MSI (s) (00:94) [15:27:21:049]: User policy value 'DisableRollback' is 0
MSI (s) (00:94) [15:27:21:049]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:94) [15:27:21:049]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:94) [15:27:21:049]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:94) [15:27:21:049]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:94) [15:27:21:049]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:94) [15:27:21:049]: Restoring environment variables
MSI (s) (00:94) [15:27:21:049]: Destroying RemoteAPI object.
MSI (s) (00:A8) [15:27:21:049]: Custom Action Manager thread ending.
MSI (c) (E4:A4) [15:27:21:049]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E4:A4) [15:27:21:049]: MainEngineThread is returning 0
=== Verbose logging stopped: 3/4/2015 15:27:21 ===Darrell H Burns
Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew
I'm unable to connect to the server.
hi
it has been a long while since i had to do a setup similar to this, and I am finding it cumbersome..
our windows cluster has 2 node on active-active & multiple instances of SQLSERVER installed (a total of 4)
while at using SSMS on this cluster i can connect to the named instance ssinst04\ssinst04 and everything is well.
however, it will not connect while i try to connect from another system.
there are no firewalls running on either system nor a firewall in between them.
the OS on both is Windows Server 2008 R2.
on the client, I can run a correct ping.
on the client, if i try testing SQLSERVER connectivity as below, i have no response:
telnet ssinst04 1433
i have checked the ports used by the server, like:
SELECT local_tcp_port
FROM sys.dm_exec_connections
WHERE session_id = @@SPID
/*
returned
1433
*/
i have set the connection on SSMS in the host server to use TCP/IP and defined the connection string as:
ssinst04\ssinst04,1433
that has worked correctly.
but the same connection string on the remote client does not work.
Yes! I have checked the tick-box for 'allow remote connections to this server'
maybe it is something very very obvious .. I am not seen.
please let me know if you have any further info.
could I please ask for some suggestions?
thanks,
data warehouse | data migration | ETL/ELT | UK | Talend http://www.brainpowered.net/
