Alternative step on Biztalk "terminator" process, regarding disabling all sql server jobs prior to running.
I am getting errors in one of the BT jobs, they recommend running a terminator tool available from MS ... One of the requirements is to disable all the sql server jobs, my question is: Can I just stop the sql server agent? Or this won't do it ....
Thanks
Bico Bielich
Hi,
I assume that you are talking about issue identified by Monitor BizTalk Server job.
Why you want to stop the sql server agent? There could be other Non-BizTalk jobs running too.
You just need to make sure that you have a BizTalk Backup of your databases, all the BTS hosts have been stopped,
BTS SQL Agent jobs have been disabled.
Refer:
http://blogs.msdn.com/b/biztalkcpr/archive/2011/02/10/using-biztalk-terminator-to-resolve-issues-identified-by-biztalk-msgboxviewer.aspx
Pls follow the link and perform action based on the respective issue reported by the
Monitor BizTalk Server job.
Rachit
Similar Messages
-
Is anyone else experiencing the same? WiFi is running fine, disabled all the Anti-Virus, still barely runs.
2013 27" iMacI'm having the same issue, mine says prepairing to backup. I let it run for 12 hours and it never performed a backup. I have a Mac Book Pro
-
I need step by step way to make replication between oracle and sql server
I succeeded in make dblink between oracle and microsoft sql
and I try to insert data using dblink to microsoft sql
what will I do now to make replication between themhow to configure my apply process to work with sql server by getway , I want to make replication
note :
I make dblink between oracle and sql and make insert from oracle to sql
is it sufficient to make replication by OEM between oracle and oracle and then add new apply process to work with gateway for sql server and how ? -
Hi All,
I would like to know what are the Drawbacks of using BizTalk Server Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition.
We are currently using Enterprise Edition.
1) Are there any adverse performance constraints? Microsoft mentions to use SQL Server Enterprise Edition for "Optimal Performance" but does not expand on the topic.
2) Any features missing?
2) Is there a supported way to downgrade SQL Enterprise to Standard for an exisiting BTS Environment?
Thanks!1) SQL Standard is limited to 4 CPU's and 64GB of memory while Enterprise is 8 CPU and 2TB or memory.
2) The only BizTalk feature dependency on a SQL Enterprise feature is BAM Real-Time Aggrigations which requires Analysis Services RTA.
3) Yes, but it's not a SQL downgrade really, you would move the BizTalk databases:
http://msdn.microsoft.com/en-us/library/aa559835.aspx -
SQL Server Job Notifications Disabled
Hi All,
This morning I noticed that my production job notifications are not configured, I used to get the alerts using the same operator before and now suddenly I see all jobs have no notifications set. Is dropping and recreating Jobs remove all Notifications? Also
when I check the operator properties it says Never e-mailed. Where can I see this history if some body did it manually? I have job alerts in my inbox received last week.
SwapnaHello,
No need to worry, everything is fine here.
If a principal is disabled, then it has a red arrow pointing down in the icon, like my "sa" account below. Here you have a red pin icon and this means you can't modify it. Since SQL Server 2014 we can create user defined server role (below "MyUserDefinedServerRole"),
which wasn't possible in SQL Server 2012 and lower version. As you can see in the screenshot below, user defined roles don't have a red pin and can be modified, while predefined server roles do have a pin:
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Date 07-01-2014 10:00:00 PM
Log Job History (NAV Backup 1.Subplan_1)
Step ID 1
Server NAVSRV
Job Name NAV Backup 1.Subplan_1
Step Name Subplan_1
Duration 00:02:26
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
1122About your question on How and Who changed it, i told that nobody changed it. I found in this way.
1122
I also Saw the plan and the path of Database and database log was ok , i mean PHARMANEXT_LOG_95ABA2F6-DC67-4CFC etc...
was exactly like in the C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA
Maybe is something wrong with my backup script, but i dont think so because before 23 of december
everithing was ok. After this date it failed.
Anyway check this script of "Remove SQL log" , the one that you think is a culprit:
DECLARE @name VARCHAR(50)
DECLARE @fileName VARCHAR(256)
DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb')
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @filename = @name + '_log'
Exec ('Use [master] alter database [' + @name + '] set recovery simple')
Exec ('Use [master] alter database [' + @name + '] set recovery FULL')
Exec ('Use [' + @name + '] DBCC SHRINKFILE ("' + @filename + '",1)')
FETCH NEXT FROM db_cursor INTO @name
END
CLOSE db_cursor
DEALLOCATE db_cursor
go
Hello,
You have created a cursor which will take all user databases and change recovery model to Simple and then to full what this will cause it will break the log chain and you might loose your RPO and RTO.This operation truncates the log .Please stop this job
immediately.It is worst you can do to your Database recovery and availability.After this you are trying to shrink .
As pointed out it is seriously not advised to shrink data file.And if you have proper trn log backup it manages the growth of log file
Hope this helps
Keep looking for any such activity which might change anything in your database
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
When I try to add the
fulltext service to a named instance in
SQLServer 2000, I see the option "Add components to your existing installation"
in gray.
I launched
the installer both ways, with the services stoped and started,
and always the same result.Please check the below link and try..
http://technet.microsoft.com/en-us/library/aa197936%28v=sql.80%29.aspx
http://www.databasejournal.com/features/mssql/article.php/3441981/Full-Text-Search-on-SQL-2000-Part-1.htm
Raju Rasagounder Sr MSSQL DBA -
Basic steps as how to web usage mine in sql server 2005
Hi there,
I am doing a project on web usage mining of my universities server logs and im just wondering how i go about mining them in sql server 2005?
Do i mine them in one table? do i normalise the web log data? what algorithms will i use on them as im trying to get usage patterns from the users and also where most of the users come from.
Thanks in advance
GaryHi
Here’re some thoughts that might help you design your Data Mining for weblogs:
1. You can put the data in one or more tables as per the semantics of the data. Data which is an entity by itself should be put in a flat table with one key per entry (user sessions on the web server for example), whereas some data naturally will have a many to one relation with the primary data (page visits per session for example) and can be put in a separate table with primary/foreign key relationship. SQL Server 2005 will model them as case table/nested table for the purpose of mining.
2. Normalize: Depends on what your data looks like. If you want to run clustering algorithm and your data has two attributes, A and B and A is 10 times more important than B, you should normalize accordingly. If the actual values of A are in order of thousand and actual values ob B are in order of tens and they are equally important, you should again normalize. However, if you want to use the as-is value without a weight, you do not have to normalize the data.
3. Usage Patterns, like a sequence of page visits can be modeled using sequence clustering algorithm. User categorization based on attributes might be a clustering algorithm. If you have more information on what you want to find out, I might be able to suggest more specific choices.
Hope this helps
Shuvro -
Message
Executed as user: CORPTST\XXXXX. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job. The error information returned
by PowerShell is: 'Security error. '. Process Exit Code -1. The step failed.
I receive this error during the sql server job 'syspolicy_purge_history' execution when sql server got upgraded form SQL Server 2008 to 2014.Hi Vishnu,
According to the error message, it also occurs in SQL Server 2012. Here is a feedback about the error in the link below.
https://connect.microsoft.com/SQLServer/feedback/details/754063/sql-server-2012-syspolicy-purge-history-job-step-3-fails-with-security-error
To resolve this issue, please change the value of the following registry key from ‘RemoteSigned’ to ‘Unrestricted’. For more details, you can review this similar
blog.
HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps120\ExecutionPolicy
Thanks,
Lydia Zhang -
SQL Server - Extract Error - OGG-00868 Supplemental logging is disabled
Hello,
We are trying to replicate from a SQL Server 2008 database to Oracle database, but when trying to start the extract process we are getting the following error message:
OGG-00868 Supplemental logging is disabled for database 'GoldenGate'. To enable logging, perform the following: 1) Set 'trunc. log on chkpt.' to false. 2) Create a full backup of the database. Please refer to the "Oracle GoldenGate For Windows and UNIX Administration Guide" for details.
I have read that for enabling the supplemental logging is enough to "add trandata table_name", and this is done, and the extract process we are using is the following:
EXTRACT cap_or4
SOURCEDB GoldenGate
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT
EXTTRAIL c:\GoldenGate\V28983-01-GG-111112-SQLServer-Windows-x64\dirdat\C4
TABLE GoldenGate.dbo.DES_T1;
And the 'trunc.log on chkpt' is set to false.
We don’t know what else to do, or to check... does anyone have any idea?!
Thank you very much, best regards,
Araitz.-Have you followed all the process for installing as per the guide? clearly you missed something
Please follow below steps.
Installation & Configuration of Oracle GoldenGate for MS SQL Server:
Pre-requisites:
1.Change Data Capture (CDC) must be enabled for Oracle GoldenGate and will be enabled by Oracle GoldenGate by means of the ADD TRANDATA command.
2.SQL Server source database must be set to use the full recovery model.
3.Oracle GoldenGate does not support system databases.
4.After the source database is set to full recovery, a full database backup must be taken.
5.SQL Server 2008 ODBC/OLE DB: SQL Server Native Client 10.0 driver
6.Oracle GoldenGate processes can use either Windows Authentication or SQL Server Authentication to connect to a database.
7.Before installing Oracle GoldenGate on a Windows system, install and configure the Microsoft Visual C ++ 2005 SP1 Redistributable Package. Make certain it
is the SP1 version of this package, and make certain to get the correct bit version for your server. This package installs runtime components of Visual C++
Libraries. For more information, and to download this package, go to http://www.microsoft.com.
Privileges:
1.Required SQL Server privileges for Manager when using Windows authentication
Extract(source system)
BUILTIN\Administrators account must be a member of the SQL Server fixed server role System Administrators.
Account must be a member of the SQL Server fixed server role System Administrators
Replicat (target system)
BUILTIN\Administrators account must be at least a member of the db_owner fixed database role of the target database.
Account must be at least a member of the db_owner fixed database role of the target database.
2.Required SQL Server privileges for Extract and Replicat when using SQL Server authentication
Extract - Member of the SQL Server fixed server role System Administrators.
Replicat - At least a member of the db_owner fixed database role of the target database.
Downloading Oracle GoldenGate
Download the appropriate Oracle GoldenGate build to each system that will be part of the Oracle GoldenGate configuration.
1. Navigate to http://edelivery.oracle.com.
2. On the Welcome page:
--Select your language.
--Click Continue.
3. On the Export Validation page:
--Enter your identification information.
--Accept the Trial License Agreement (even if you have a permanent license).
--Accept the Export Restrictions.
--Click Continue.
4. On the Media Pack Search page:
--Select the Oracle Fusion Middleware Product Pack.
--Select the platform on which you will be installing the software.
--Click Go.
5. In the Results List:
--Select the Oracle GoldenGate Media Pack that you want.
--Click Continue.
6. On the Download page:
--Click Download for each component that you want. Follow the automatic download
process to transfer the mediapack.zip file to your system.
Installing the Oracle GoldenGate files
1. Unzip the downloaded file(s) by using WinZip or an equivalent compression product.
2. Move the files in binary mode to a folder on the drive where you want to install Oracle GoldenGate. Do not install Oracle GoldenGate into a folder that contains spaces in its name, even if the path is in quotes. For example:
C:\“Oracle GoldenGate” is not valid.
C:\Oracle_GoldenGate is valid.
3. From the Oracle GoldenGate folder, run the GGSCI program.
4. In GGSCI, issue the following command to create the Oracle GoldenGate working
directories.
CREATE SUBDIRS
a.Create the necessary working directories for GG.
Source DB:
GGSCI>create subdirs
Target DB:
GGSCI>create subdirs
Install the GoldenGate Manager process
1.Create a GLOBALS parameter file
--Execute the following commands from the <install location>.
GGSCI> EDIT PARAMS ./GLOBALS
--In the text editor, type the following:
MGRSERVNAME <mgr service>
Using a GLOBALS file in each GoldenGate instance allows you to run multiple Managers as services on Windows. When the service is installed, the Manager name
is referenced in GLOBALS, and this name will appear in the Windows Services control panel.
Note! Check to ensure that the GLOBALS file has been added in the GoldenGate installation directory and that it does not have an extension.
--Execute the following command to exit GGSCI.
GGSCI> EXIT
2. Install the Manager service
Execute the following command to run GoldenGate’s INSTALL.EXE . This executable installs Manager as a Windows service and adds GoldenGate events to the
Windows Event Viewer.
Shell> INSTALL ADDSERVICE ADDEVENTS
Note: Adding the Manager as a service is an optional step used when there are multiple environments on the same system or when you want to control the name
of the manager for any reason.
Configuring an ODBC connection
A DSN stores information about how to connect to a SQL Server database through ODBC (Open Database Connectivity). Create a DSN on each SQL Server source
and target system.
NOTE: Replicat will always use ODBC to query the target database for metadata.
To create a SQL Server DSN
1. Run one of the following ODBC clients:
--If using a 32-bit version of Oracle GoldenGate on a 64-bit system, create the DSN by running the ODBCAD32.EXE client from the %SystemRoot%\SysWOW64
folder.
--If using a 64-bit version of Oracle GoldenGate on a 64-bit system, create a DSN by running the default ODBCAD32.EXE client in Control Panel>Administrative
Tools>Data Sources (ODBC).
--If using a version of Oracle GoldenGate other than the preceding, use the default ODBC client in Control Panel>Administrative Tools>Data Sources (ODBC).
2. In the ODBC Data Source Administrator dialog box of the ODBC client, select the System DSN tab, and then click Add.
3. Under Create New Data Source, select the correct SQL Server driver as follows:
--SQL Server 2000: SQL Server driver
--SQL Server 2005: SQL Native Client driver
--SQL Server 2008: SQL Server Native Client 10.0 driver
4. Click Finish. The Create a New Data Source to SQL Server wizard is displayed.
5. Supply the following:
--Name: Can be of your choosing. In a Windows cluster, use one name across all nodes in the cluster.
--Server: Select the SQL Server instance name.
6. Click Next.
7. For login authentication, select With Windows NT authentication using the network login ID for Oracle GoldenGate to use Windows authentication, or select
With SQL Server authentication using a login ID and password entered by the user for Oracle GoldenGate to use database credentials. Supply login information
if selecting SQL Server authentication.
8. Click Next.
9. If the default database is not set to the one that Oracle GoldenGate will connect to,
click Change the default database to, and then select the correct name. Set the other
settings to use ANSI.
10. Click Next.
11. Leave the next page set to the defaults.
12. Click Finish.
13. Click Test Data Source to test the connection.
14. Close the confirmation box and the Create a New Data Source box.
15. Repeat this procedure from step 1 on each SQL Server source and target system.
Setting the database to full recovery model
Oracle GoldenGate requires a SQL Server source database to be set to the full recovery model.
To verify or set the recovery model
1. Connect to the SQL Server instance with either Enterprise Manager for SQL Server 2000 or SQL Server Management Studio for SQL Server 2005 and 2008.
2. Expand the Databases folder.
3. Right-click the source database, and then select Properties.
4. Select the Options tab.
5. Under Recovery, set Model to Full if not already.
6. If the database was in Simple recovery or never had a Full database backup, take a Fulldatabase backup before starting Extract.
7. Click OK.
Enabling supplemental logging
These instructions apply to new installations of Oracle GoldenGate for all supported SQL Server versions. You will enable supplemental logging with the ADD
TRANDATA command so that Extract can capture the information that is required to reconstruct SQL operations on the target. This is more information than
what SQL Server logs by default.
--SQL Server 2005 updated to CU6 for SP2 or later: ADD TRANDATA calls the sys.sp_extended_logging stored procedure.
--SQL Server 2005 pre-CU6 for SP2: ADD TRANDATA creates the following:
A replication publication named [<source database name>]: GoldenGate<source database name> Publisher. To view this publication, look under Replication>Local
Publications in SQL Server Management Studio. This procedure adds the specified table to the publication as an article.
A SQL Server Log Reader Agent job for the publication. This job cannot run concurrently with an Extract process in this configuration.
--SQL Server 2008: ADD TRANDATA enables Change Data Capture (CDC) and creates a minimal Change Data Capture on the specified table.
a.Oracle GoldenGate does not use the CDC tables other than as necessary to enablesupplemental logging.
b.As part of enabling CDC, SQL Server creates two jobs per database: <dbname>_capture and <dbname>_cleanup. The <dbname>_capture job adjusts the secondary
truncation point and captures data from the log to store in the CDC
tables. The <dbname>_cleanup job ages and deletes data captured by CDC.
c.Using the TRANLOGOPTIONS parameter with the MANAGESECONDARYTRUNCATIONPOINT option for Extract removes the <dbname_capture> job, preventing the overhead of
the job loading the CDC tables.
d.The alternative (using TRANLOGOPTIONS with NOMANAGESECONDARYTRUNCATIONPOINT) requires the SQL Server Agent to be running and requires the <dbname>_capture and <dbname>_cleanup jobs to be retained. You will probably need to adjust the <dbname>_cleanup data retention period if the default of three days is not acceptable for storage concerns.
To enable supplemental logging
1. On the source system, run GGSCI.
2. Log into the database from GGSCI.
DBLOGIN SOURCEDB <DSN>[, USERID <user>, PASSWORD <password>]
Where:
-- SOURCEDB <DSN> is the name of the SQL Server data source.
-- USERID <user> is the Extract login and PASSWORD <password> is the password that is required if Extract uses SQL Server authentication.
3. In GGSCI, issue the following command for each table that is, or will be, in the Extract configuration. You can use a wildcard to specify multiple table
names, but not owner names.
ADD TRANDATA <owner>.<table>
NOTE:The Log Reader Agent job cannot run concurrently with the GoldenGate Extract process.
4.Configuration
a.Create and start manager on the source and the destination.
Source DB:
shell>ggsci
GGSCI> edit params mgr
PORT 7809
DYNAMICPORTLIST 7900-7950
DYNAMICPORTREASSIGNDELAY 5
AUTOSTART ER *
AUTORESTART ER *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 30
LAGCRITICALMINUTES 60
LAGREPORTMINUTES 30
PURGEOLDEXTRACTS c:\ogg\dirdat\T*, USECHECKPOINTS, MINKEEPFILES 10
GGSCI> start manager
GGSCI>info all
b. Create the extract group on the source side:
GGSCI> edit params EXT1
Add the following lines to the new parameter file
EXTRACT EXT1
SOURCEDB <DSN>, USERID ogg, PASSWORD ogg@321!
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT
EXTTRAIL c:\ogg\dirdat\T1
DISCARDFILE c:\ogg\dirrpt\EXT1.DSC, PURGE, MEGABYTES 100
TABLE dbo.TCUSTMER;
TABLE dbo.TCUSTORD;
GGSCI>ADD EXTRACT EXT1, TRANLOG, BEGIN NOW
GGSCI>ADD EXTTRAIL c:\ogg\dirdat\T1, EXTRACT EXT1, MEGABYTES 100
GGSCI> edit params PMP1
Add the following lines to the new parameter file
EXTRACT PMP1
SOURCEDB <DSN>, USERID ogg, PASSWORD ogg@321!
PASSTHRU
RMTHOST dr, MGRPORT 7810
RMTTRAIL c:\ogg\dirdat\P1
TABLE dbo.TCUSTMER;
TABLE dbo.TCUSTORD;
GGSCI> ADD EXTRACT PMP1, EXTTRAILSOURCE c:\ogg\dirdat\T1
GGSCI> ADD EXTTRAIL c:\ogg\dirdat\P1, EXTRACT PMP1, MEGABYTES 100
Target DB:
===========
shell>ggsci
GGSCI> edit params mgr
PORT 7810
AUTOSTART ER *
AUTORESTART ER *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 30
LAGCRITICALMINUTES 60
LAGREPORTMINUTES 30
PURGEOLDEXTRACTS c:\ogg\dirdat\P*, USECHECKPOINTS, MINKEEPFILES 10
GGSCI> start manager
GGSCI>info all
Create parameter file for replicat:
GGSCI> edit params REP1
REPLICAT REP1
ASSUMETARGETDEFS
TARGETDB <dsn>, USERID ogg@DR, PASSWORD ogg@321!
DISCARDFILE c:\ogg\dirrpt\REP1.DSC, append, megabytes 100
HANDLECOLLISIONS
ASSUMETARGETDEFS
MAP dbo.TCUSTMER, TARGET dbo.TCUSTMER;
MAP dbo.TCUSTORD, TARGET dbo.TCUSTORD;
GGSCI>ADD REPLICAT REP1, RMTTRAIL c:\ogg\dirdat\P1, nodbcheckpoint
# Start extract and replicat:
Source:
GGSCI> start er *
Destination:
GGSCI> start er *Greetings,
N K -
I have a SSIS package that fails when running via sql server agent. I can successfully run it from BIDS. I have created a proxy account that is in the local server administrators group and is sysadmin. SQL Server Agent and SQL
Server Integration Services are running under the same account,
following the the error message:
Error: 2014-02-07 10:29:12.59
Code: 0xC0029151
Source: Execute De-linking Execute Process Task
Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
End Error
This package ran successfully on a different server running windows 2003 and sql server 2008 r2. The new environment is windows 7 with sql server 2008 r2.Hi Gaileg,
As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
SQL Server Agent rather than the SSIS package itself.
Regards,
Mike Yin
TechNet Community Support -
I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-PC
Machine processor count: 4
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
SQL Server 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
HELP: 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: SS2012
INSTANCENAME: SS2012
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htmPlease help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm -
i downloaded Microsoft visual studio 2010 in my laptop for windows 8 and in that the sql server is not working.the services for sql server is not starting .so pls help me in starting the services for sql server.
1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
7. Check firewall settings if step 5 or 6 connectivity test fails
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
Hello Everyone !
I am looking for a way to disable all jobs in grid control and then re-enable all.
Your help is much appreciated.
Regards
NeoAre you looking to disable all of the Jobs submitted thru EM? Or the background jobs that EM runs via DBMS_JOBS (10/11g) or DBMS_SCHEDULER (12c) ??
-
Access SQL Server data at time of Windows OS Boot Process
It is possible to access SQL Server data at time of Windows OS Boot Process and before login into Windows.
if anybody any idea on this.
If you think my suggestion is useful, please rate it as helpful.
If it has helped you to resolve the problem, please Mark it as Answer.
Varinder Sandhu www.varindersandhu.inNo, you need to identified before accessing to SQL Server. It is like you try turn on electric cooker before you open the door.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence
Maybe you are looking for
-
How to change the default name of new adjustment layers? (and other Q's)
How do I change the default name of new adjustment layers? How can I make it so that adjustment layers don't come with a mask when I create them (unless I have a selection active)? Why isn't the Shadows/Highlights functionality an adjustment layer? I
-
Help me troublesho​ot my CalDAV Calendar
Hello. I have a Synology NAS which hosts my personal email server and calendar (CalDAV) server. I have connected to the CalDAV server with my other devices (2 Windows and 2 Linux computers running Thunderbird/Lightning; Apple iPod touch). My Z10 conn
-
Get error message when I try to plug in my newly updated iphone top my PC
Just installed the new os7 on my phone and now when I plight it into my PC I get an error message. "The iPhone cannot be used because it requires iTunes version 11.1 or later. Go to www.itunes.com to download the latest version of iTunes." What do I
-
Material Master Data from R/3
Hi BW Gurus, I am trying to upload 0material_attr data from r/3 to BW. I am doing good upto replicating master data in BW, but after that I dont know how to follow steps. Please if any one know how to load the master data after replicatin
-
Mac Pro does not wakeup 1 of 3 connected monitors: Philips times out
Hi, (Setup) I use a Mac Pro from 2014 (End 2013, AMD Firepro, D700 Graphics, 6core, 1TB SSD, 32MB, actual OSX Yosemite 10.10.2). Connected are three monitors: Philips BDM 4065 UC (40 great inches) via mini DP to DP cable 2x Dell 2410 (vertical/pivot