Error in executing Database Check on SRM Server (BRCONNECT)

Dear All,
When executing the Database check by DB13 or BRTOOLS I am getting the following Error.
BR0477I Oracle pfile /oracle/FRP/102_64/dbs/initFRP.ora created from spfile /oracle/FRP/102_64/dbs/spfileFRP.ora
BR1301W Error message from likeywlib:
===...could not load SSF library libsapsecu.o .
BR1301W Error message from likeywlib: likey_init:Couldn't load SAPSECULIB ("libsapsecu.o") using function SsfSupInit (), rc = 1
BR1302E Initialization of license key library likeywlib failed, return code 1
BR0602E No valid SAP license found - please contact SAP
BR0806I End of BRCONNECT processing: cegxjpxo.log2011-10-03 14.02.25
BR0280I BRCONNECT time stamp: 2011-10-03 14.02.25
BR0804I BRCONNECT terminated with errors
I have following profile parameters
ssl/ssl_lib                           /usr/sap/FRP/SYS/exe/run/libsapcrypto.o
ssf/ssfapi_lib     /usr/sap/FRP/SYS/exe/run/libsapcrypto.o
sec/libsapsecu                  /usr/sap/FRP/SYS/exe/run/libsapcrypto.o
ssf/name                          SAPSECULIB
I have maintained DIR_LIBRARY as Environment variable with /usr/sap/FRP/SYS/exe/run and all the library files are maintained at above said location including libsapsecu.o which have 777 permission at AIX level.
Please Helpu2026u2026u2026u2026u2026..
Regards,
Manish Sachan

Thanks, Sunny
Problem has been solved by the help of your suggested NOTE....................
Regards,
Manish Sachan

Similar Messages

Error when executing database check using brconnect or in DB13.

Dear Experts,
I am facing problem in executing database check using brconnect or in DB13.
I get the following error:-
I am giving the last few lines where the error comes
G:\oracle\MRP\sapbackup 6 52228060 20440724 60.86 0 0
G:\oracle\MRP\sapcheck 6 52228060 20440724 60.86 0 0
G:\oracle\MRP\sapreorg 6 52228060 20440724 60.86 0 0
BR0252E Function _stat() failed for 'G:\oracle\MRP\saptrace' at location BrDiskStatGet-1
BR0253E errno 2: No such file or directory
BR0277E Determination of disk volume status for G:\oracle\MRP\saptrace failed
BR0806I End of BRCONNECT processing: cdvnwuiw.chk 2007-06-23 16.45.39
BR0280I BRCONNECT time stamp: 2007-06-23 16.45.39
BR0804I BRCONNECT terminated with error
This is the config path in my init<sid>.ora.
*._OPTIM_PEEK_USER_BINDS=FALSE
*.background_dump_dest='F:\oracle\MRP\saptrace\background'
*.compatible='10.2.0'
*.control_file_record_keep_time=30
*.control_files='G:\oracle\MRP\origlogA\cntrl\cntrlMRP.dbf','G:\oracle\MRP\origlogB\cntrl\cntrlMRP.dbf','G:\oracle\MRP\sapdata1\cntrl\cntrlMRP.dbf'
*.core_dump_dest='F:\oracle\MRP\saptrace\background'
*.db_block_size=8192
*.db_cache_size=281699942
*.db_files=254
*.db_name='MRP'
*.dml_locks=4000
*.event='10191 trace name context forever, level 1'
*.FILESYSTEMIO_OPTIONS='setall'
*.job_queue_processes=1
*.log_archive_dest='F:\oracle\MRP\oraarch\MRParch'
*.log_buffer=1048576
*.log_checkpoint_interval=0
*.log_checkpoints_to_alert=true
*.open_cursors=800
*.optimizer_features_enable='10.2.0.1'
*.pga_aggregate_target=375599923
*.processes=80
*.recyclebin='off'
*.remote_login_passwordfile='exclusive'
*.remote_os_authent=true
*.sessions=96
*.sga_max_size=563399884
*.shared_pool_reserved_size=28169994
*.shared_pool_size=281699942
*.sort_area_retained_size=0
*.sort_area_size=2097152
*.statistics_level='typical'
*.undo_management='AUTO'
*.undo_retention=43200
*.undo_tablespace='PSAPUNDO'
*.user_dump_dest='F:\oracle\MRP\saptrace\usertrace'
*.workarea_size_policy='AUTO'
The path in my system is same as mentioned in the init<sid>.ora
Please help me to find out cause of the error.
Thanks

Dear Mr. Yaroslav,
Thanks,
I have checked in <sid>adm user since we have looged in the same user Id.
There was no entrie for the SAPTRACE in environmental variable.
I have inserted and given the requried path"F:\oracle\MRP\saptrace".
Thankyou....hope in my next restart of the server it will work....

Error in the database check.

hi all,
I am getting following error while doing Database check in my system:
BR0976W Database message alert - level: ERROR, line: 7649, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7650, time: 2010-08-26 22.56.27, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7654, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7657, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7658, time: 2010-08-26 22.56.27, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7662, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7669, time: 2010-08-26 22.56.27, message:
ORA-16038: log 1 sequence# 28567 cannot be archived
BR0976W Database message alert - level: ERROR, line: 7670, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "", blockno (blocksize=)
BR0976W Database message alert - level: ERROR, line: 7675, time: 2010-08-26 22.56.27, message:
ORA-16038: log 1 sequence# 28567 cannot be archived
BR0976W Database message alert - level: ERROR, line: 7676, time: 2010-08-26 22.56.27, message:
ORA-19502: write error on file "", blockno (blocksize=)
BR0976W Database message alert - level: ERROR, line: 7686, time: 2010-08-26 22.57.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7687, time: 2010-08-26 22.57.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7691, time: 2010-08-26 22.57.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7694, time: 2010-08-26 22.57.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7695, time: 2010-08-26 22.57.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7699, time: 2010-08-26 22.57.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7709, time: 2010-08-26 22.58.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7710, time: 2010-08-26 22.58.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7714, time: 2010-08-26 22.58.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7717, time: 2010-08-26 22.58.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7718, time: 2010-08-26 22.58.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7722, time: 2010-08-26 22.58.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7734, time: 2010-08-26 22.59.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7735, time: 2010-08-26 22.59.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7739, time: 2010-08-26 22.59.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7742, time: 2010-08-26 22.59.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7743, time: 2010-08-26 22.59.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7747, time: 2010-08-26 22.59.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7757, time: 2010-08-26 22.59.04, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7758, time: 2010-08-26 22.59.04, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7762, time: 2010-08-26 22.59.04, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7765, time: 2010-08-26 22.59.04, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7766, time: 2010-08-26 22.59.04, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7770, time: 2010-08-26 22.59.04, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7780, time: 2010-08-26 23.00.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7781, time: 2010-08-26 23.00.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7785, time: 2010-08-26 23.00.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7798, time: 2010-08-26 23.00.10, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7799, time: 2010-08-26 23.00.10, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7803, time: 2010-08-26 23.00.10, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7811, time: 2010-08-26 23.01.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7812, time: 2010-08-26 23.01.02, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7816, time: 2010-08-26 23.01.02, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7826, time: 2010-08-26 23.02.03, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7827, time: 2010-08-26 23.02.03, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7831, time: 2010-08-26 23.02.03, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7839, time: 2010-08-26 23.03.03, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7840, time: 2010-08-26 23.03.03, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7844, time: 2010-08-26 23.03.03, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7857, time: 2010-08-26 23.03.42, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7858, time: 2010-08-26 23.03.42, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7862, time: 2010-08-26 23.03.42, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7870, time: 2010-08-26 23.04.03, message:
ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
BR0976W Database message alert - level: ERROR, line: 7871, time: 2010-08-26 23.04.03, message:
ORA-27063: number of bytes read/written is incorrect
BR0976W Database message alert - level: ERROR, line: 7875, time: 2010-08-26 23.04.03, message:
BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB)
BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
What are these and how to rectify these?
Regards,
Priya

Hi Priya,
When you perform database check either using brtools or in tx code db13, SAP will check the health of database system by reading the content of alert_<SID>.log file located in /oracle/<SID>/saptrace/background. Also it checks the contents of database parameters as per the threshold configuration in tx code db17.
The content of oracle alert log file showed that it cannot write archive log file.. Please see the content of alert_<SID>.log file and correct the archive log error creation. The error indicates that either disk block is corrupted or damaged.
As seen in the error message the error message was created in the month of Aug 2010 and appended in the alert_IRQ.log file located in /oracle/IRQ/saptrace/background.If the error is not present now and if you want to perform database check, then delete old contents from the first line to till last month in alert_IRQ.log file using operating system. Then save the file and Then perform database check again.
Please make sure you must monitor database check daily and ensure that if the error occurs for writing archive log file, it is dangerous as archive will stuck and the whole operation hangs.
The message below is for warning and this can be ignored and this is becasue of threshold configuration. You may change the threshold configuration in tx code db17.
However warning " WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB) BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file) BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096) BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE) BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE ( FALSE) BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE ( TRUE) BR0978W Database profile alert - level: WARNING, parameter" - is for warning only it could be bug problems. SO there is no need to correct the problem.
Hope this helps you.
Thanks and Regards
apr

Want to upgrade 2008 R2 to 2012. Upgrade advisor giving errors relating to Database Compatability Level and Server Collation

I want to upgrade a SQL Server from 2008 R2 to 2012. When I run upgrade advisor, I get the following error messages:
Rule "Valid Database compatibility level and successful connection" failed.
The report server database is not a supported compatibility level or a connection cannot be established. Use Reporting Services Configuration Manager to verify the report server configuration and SQL Server management tools to verify the compatibility
level.
Rule "Valid Database server collation and successful connection" failed.
The SQL Server Database Engine is not configured with a valid server collation and cannot be used as the Reporting Services SharePoint Shared Service catalog database.
The database called ReportServer has Collation = Latin1_General_Cl_AS_KS_WS and Compatibility level = 100

Hi Andrew,
Regarding to the first error message, please check the Reporting Service Configuration Manager, make sure that you connect to ReportServer database from the correct server
and use servername\instancename format connection string. For more details, please review this similar
thread.
Regarding to the second error, it is caused by that the current SQL Server Database Engine server is using an incompatible server collation.
SQL Server 2012 Reporting Services SharePoint mode utilizes the SharePoint shared services architecture. SharePoint does not support SQL Server Database Engine configured for case sensitive or server collations or binary server collations.
And since the SQL Server Database Engine server collation property cannot be changed, you will not be able to complete an upgrade of Reporting Services. You will need to migrate your Reporting Services installation to a new server which is using a compatible
server collation. For more details, please review the following article:
Incompatible Database Engine Server Collation:
https://msdn.microsoft.com/en-us/library/hh759335%28v=sql.110%29.aspx?f=255&MSPPError=-2147217396
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Error when execute a package from SQL Server Agent

We have the next problem:
When we execute a package from a Job of SQL Server agent, it shows the success messege, but reviewing the results, the package didnt do all the tasks.
When we run it mannually by MSIS the package, it shows the success message and it works fine.
The workflow of the package is :
1) Shrink the databases (executing a sql file)
2) Backup the databases (Back up Database task of MSIS)
3) Rename the files to .BAK extension (by the Foreach loop container and fyle system task)
4) Execute command to compress the it (by a .bat)
5) Move the compress file to another location (by another Foreach loop)
Manually run correct, but when is a a SQL AGent Job that execute the package it does only the first 2 steps.
we are ussing Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (coffee) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
We are using a user with administrator privilegies
Cheers

Can you check if account running package has proper access. You may need to define a proxy account for that.
See
http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
http://gqbi.wordpress.com/2014/01/30/setting-up-a-proxy-account-to-run-sql-server-integration-services-ssis-2012-packages/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Error while executing program "BBP_STARTUP_TOOL_FOR_CCMS" in SRM 5.

Hi,
I get an error message "Error starting appl. monitor for client 000 and 001; processing terminated." when i execute the program. BBP_STARTUP_TOOL_FOR_CCMS
I m not getting wats the problem. Pls help me with so.
Thanks
Regards.

Hi Prasanna,
Check the below SAp Note:
SAP Note : 1030657
Thanks,
Vijay.

[b]Error in installation database in Windows 2003 server[/b]

Hi, I have a problem. I am trying to install a database Oracle Enterprise Edition 10.1.0.2.0 in a machine that has Windows 2003 Server. On having finished the installation and begin the Database Configuration Assistant appears the error ora-12546 TNS permission denied. In the file listener.log
the following messages appear:
TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12546: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00516: Permission denied
32-bit Windows Error: 5: Input/output error
In the alert.log appear:
OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified O/S-Error: (OS 1) Incorrect function. !
I install in local mode, not remote and using Administrator user.
Help me, please!
Regards
Carlos

Hello,
There is a note in SAP that indicates that EMT64/x64 is not compatible with Oracle 9.2 (nota 12546) There is Oracle's FAQ that indicates Oracle's versions and Windows that he(she) supports EMT64.
http://www.oracle.com/technology/tech/windows/faq.html#x86-64
Since you can see it(he,she) indicates that Oracle 9.2 is supported in Windows 32 bits with technology EMT64
And that alone the version 10g 2 be reread it(he,she) is compatible with Windows 2003 SEVER 64 bits with technology EMT64
I hope that this costs(suits) us to solve our problems
A greeting

Error in installation database in Windows 2003 server 64 bits

Hi, I have a problem. I am trying to install a database Oracle Enterprise Edition 9.2.6 in a machine that has Windows 2003 Server 64 bits
. On having finished the installation and begin the Database Configuration Assistant appears the error ora-12546 TNS permission denied. In the file listener.log
the following messages appear:
TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12546: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00516: Permission denied
32-bit Windows Error: 5: Input/output error
I see the note 722966 and my procesador is EM64T
I install in local mode, not remote and using Administrator user.
Help me, please!

Hello,
There is a note in SAP that indicates that EMT64/x64 is not compatible with Oracle 9.2 (nota 12546) There is Oracle's FAQ that indicates Oracle's versions and Windows that he(she) supports EMT64.
http://www.oracle.com/technology/tech/windows/faq.html#x86-64
Since you can see it(he,she) indicates that Oracle 9.2 is supported in Windows 32 bits with technology EMT64
And that alone the version 10g 2 be reread it(he,she) is compatible with Windows 2003 SEVER 64 bits with technology EMT64
I hope that this costs(suits) us to solve our problems
A greeting

Help to resolve error in sending database email from SQL Server 2012.

Please help to resolve error in sending email from SQL Server 2012.
SQL Instance Version:
Microsoft SQL Server 2012 (SP1) - 11.0.3449.0 (X64)
Jun 29 2014 23:15:18
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
Error Message: Error MeThe mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2015-01-15T19:48:25). Exception Message:
Cannot send mails to mail server. (The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated).)

The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1
Client was not authenticated).
I think the error message is pretty clear, you have to setup authentication for the SMTP connection in Database Mail, see
Database Mail Configuration Objects
Olaf Helper
[ Blog] [ Xing] [ MVP]

Restore database Error when restoring database to a new server

Hi folks,
I am oracle 10g on an AIX server (5.3).
I created an rman backup of a database. I then copied it over to a new server where I am trying to restore it (I just created the backup today). However, I am getting the error below.
Essentially, I used an initdb.ora file to create an instance of the database, and mounted it, on the new server. And then I ran a simple "restore database" command, the end of which is displayed below, with a "Restore complete. ..."
I have looked up this error (ora-01152) online and I cannot find a scenario which best provides me with a fix to my problem, about the file not being restored from a sufficiently old backup. Could any one help please?
piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
channel ORA_DISK_2: restored backup piece 1
piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
Finished restore at 14-JUN-10
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/14/2010 17:48:12
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DGROUP1/testdb/datafile/system.751.721679898'Edited by: efachim2 on Jun 15, 2010 2:19 AM

I ran only as below because I copied over the backup right after it finished, when there were no archivelogs.
RMAN> restore database;
Starting restore at 14-JUN-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=651 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=650 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=649 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=648 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00002 to +DGROUP1/testdb/datafile/undots1.667.721227421
channel ORA_DISK_1: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full
channel ORA_DISK_2: starting datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
restoring datafile 00007 to +DGROUP1/testdb/datafile/a1_x.641.721227553
restoring datafile 00009 to +DGROUP1/testdb/datafile/ent_sm01_x.659.721227557
restoring datafile 00013 to +DGROUP1/testdb/datafile/in01_x.657.721227569
restoring datafile 00015 to +DGROUP1/testdb/datafile/cs01_x.656.721227571
restoring datafile 00016 to +DGROUP1/testdb/datafile/cs01_d.650.721227559
restoring datafile 00021 to +DGROUP1/testdb/datafile/h01_x.644.721227575
restoring datafile 00023 to +DGROUP1/testdb/datafile/doc01_x.647.721227575
restoring datafile 00025 to +DGROUP1/testdb/datafile/og01_x.645.721227577
channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full
channel ORA_DISK_3: starting datafile backupset restore
channel ORA_DISK_3: specifying datafile(s) to restore from backup set
restoring datafile 00003 to +DGROUP1/testdb/datafile/sysaux.662.721227423
restoring datafile 00006 to +DGROUP1/testdb/datafile/a01_d.639.721227549
restoring datafile 00010 to +DGROUP1/testdb/datafile/ent_lg01_d.666.721227423
restoring datafile 00012 to +DGROUP1/testdb/datafile/in01_d.658.721227511
restoring datafile 00014 to +DGROUP1/testdb/datafile/cs01_d.661.721227521
restoring datafile 00019 to +DGROUP1/testdb/datafile/ndata_x.654.721227423
restoring datafile 00022 to +DGROUP1/testdb/datafile/doc_01_d.660.721227531
restoring datafile 00029 to +DGROUP1/testdb/datafile/in01_x.642.721227471
channel ORA_DISK_3: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full
channel ORA_DISK_4: starting datafile backupset restore
channel ORA_DISK_4: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DGROUP1/testdb/datafile/system.655.721227423
restoring datafile 00004 to +DGROUP1/testdb/datafile/users.653.721227453
restoring datafile 00005 to +DGROUP1/testdb/datafile/tools.663.721227423
restoring datafile 00008 to +DGROUP1/testdb/datafile/en_sm01_d.665.721227473
restoring datafile 00018 to +DGROUP1/testdb/datafile/n_data_d.664.721227423
restoring datafile 00020 to +DGROUP1/testdb/datafile/hfig01_d.652.721227527
restoring datafile 00024 to +DGROUP1/testdb/datafile/og01_d.651.721227535
restoring datafile 00028 to +DGROUP1/testdb/datafile/in1_d.646.721227469
channel ORA_DISK_4: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full
channel ORA_DISK_2: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_2: restore complete, elapsed time: 00:00:27
channel ORA_DISK_2: starting datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
restoring datafile 00017 to +DGROUP1/testdb/datafile/cs_lg01_x.640.721227579
restoring datafile 00026 to +DGROUP1/testdb/datafile/am1_d.643.721227581
restoring datafile 00027 to +DGROUP1/testdb/datafile/am1_x.671.721227581
channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full
channel ORA_DISK_2: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_2: restore complete, elapsed time: 00:00:07
channel ORA_DISK_2: starting datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
restoring datafile 00011 to +DGROUP1/testdb/datafile/ent_lg01_x.648.721227421
channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full
channel ORA_DISK_1: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_1: restore complete, elapsed time: 00:02:30
channel ORA_DISK_3: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_3: restore complete, elapsed time: 00:03:15
channel ORA_DISK_4: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
channel ORA_DISK_2: restored backup piece 1
piece handle=/ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
Finished restore at 14-JUN-10
RMAN> alter database open resetlogs;

Check database integrity throws 665 error when executing check database integrity task in SSMS.

I have read all other cases that relate to this error and cannot get this to work. Running SQL Server 2012 sp1 on Windows server 2012 R2. Disk space and permissions are fine, but I get the error below when I try and use the check database integrity task
within my maintenance plan on both system and user databases. I have researched this and fragmentation is not the issue. I'm lost at this point and would appreciate at least some steps to try. databases are not "read only" as I have read this may
contribute to the problem. All other maintenance tasks run fine.
Error message from SQL LOG
Check Database integrity on Local server connection
Databases: All system databases
Task start: 2014-01-13T11:00:04.
Task end: 2014-01-13T11:00:04.
Failed:(-1073548784) Executing the query "DBCC CHECKDB(N'master', NOINDEX)
" failed with the following error: "A database snapshot cannot be created because it failed to start.
A database snapshot cannot be created because it failed to start.
MODIFY FILE encountered operating system error 665(The requested operation could not be completed due to a file system limitation) while attempting to expand the physical file 'E:\\SQLdata\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA\\master.mdf:MSSQL_DBCC9'.
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
The database could not be exclusively locked to perform the operation.
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous
errors for more details.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Error Message from Log File Viewer in SSMS:
Source: Check Database Integrity Task      Executing query "USE [ReportServer] ".: 50% complete End Progress Error: 2014-01-13 11:31:54.92     Code: 0xC002F210
Source: Check Database Integrity Task Execute SQL Task     Description: Executing the query "DBCC CHECKDB(N'ReportServer') WITH NO_INFOMSGS " failed with the following error: "A database snapshot cannot be created
because it failed to start. A database snapshot cannot be created because it failed to start. MODIFY FILE encountered operating system error 665(The requested operation could not be completed due to a file system limitation) while attempting to
expand the physical file 'E:\SQLdata\MSSQL11.MSSQLSERVER\MSSQL\DATA\ReportServer.mdf:MSSQL_DBCC9'. The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not
support sparse files or alternate streams. Attempting to get exclusive access to run checks offline. The database could not be exclusively locked to perform the operation. Check statement aborted. The database could not be checked as a database
snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Progress: 2014-01-13 11:31:54.93     Source: Check Database Integrity Task
Executing query "USE [ReportServerTempDB] ".: 50% complete End Progress Error: 2014-01-13 11:31:55.02     Code: 0xC002F210     Source: Check Database Integrity Task Execute SQL Task
Description: Executing the query "DBCC CHECKDB(N'ReportServerTempDB') WITH NO_INFOM..." failed with the following error: "A database snapshot cannot be created because it failed to start. A database snapshot cannot be created because
it failed to start. MODIFY FILE encountered operating system error 665(The requested operation could not be completed due to a file system limitation) while attempting to expand the physical file 'E:\SQLdata\MSSQL11.MSSQLSERVER\MSSQL\DATA\ReportServerTempDB.mdf:MSSQL_DBCC9'.
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Progress: 2014-01-13 11:31:55.02     Source:
Check Database Integrity Task      Executing query "USE [AddressUpload] ".: 50% complete End Progress Error: 2014-01-13 11:31:55.13     Code: 0xC002F210     Source:
Check Database Integrity Task Execute SQL Task     Description: Executing the query "DBCC CHECKDB(N'AddressUpload') WITH NO_INFOMSGS " failed with the following error: "A database snapshot cannot be created because
it failed to start. A database snapshot cannot be created because it failed to start. MODIFY FILE encountered operating system error 665(The requested operation could not be completed due to a file system limitation) while attempting to expand
the physical file 'E:\SQLData\MSSQL11.MSSQLSERVER\MSSQL\DATA\database1.mdf:MSSQL_DBCC9'. The database snapshot for online checks could not be created. Either th... The package execution fa... The step failed.

ReFS is NOT supported in use with SQL Server 2012. Once such item, which you've stumbled upon is the fact that alternate streams and sparse files are not implemented in ReFS and thus these issues are caused. You *could* force the checkdb to execute by using
WITH TABLOCKX but that'll require exclusive access to the database for the duration of the checkdb scan and that's not something I would advise to do.
Sean Gallardy | Blog |
Twitter

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
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 Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
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\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
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\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Fatal error while executing the DQS installer on SQL Server 2014

Hi all.
I am receiving the following error when attempting to install DQS on the following platform:
Windows Server 2012
Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
(no entries in event viewer)
Error is:
[4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
to an instance of an object.
 at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
 at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
 at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
 at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
 at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
 --- End of inner exception stack trace ---
 at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
 at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
 at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
 at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
 at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
Thanks for any advice you can give.
Full log below:
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.
[4/15/2015 7:58:20 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
[4/15/2015 7:58:20 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
[4/15/2015 7:58:20 AM] Using instance: DW01, catalog: DQS.
[4/15/2015 7:58:20 AM] Executing action: Validate collation argument.
[4/15/2015 7:58:20 AM] Action 'Validate collation argument' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Check whether system reboot is pending.
[4/15/2015 7:58:20 AM] Action 'Check whether system reboot is pending' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Create data quality event source.
[4/15/2015 7:58:20 AM] Action 'Create data quality event source' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Request Database Master Key password from user..
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.
[4/15/2015 8:39:59 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
[4/15/2015 8:39:59 AM] Parsing DqsInstaller command line arguments.
[4/15/2015 8:39:59 AM] Setting the catalog to default value: DQS
[4/15/2015 8:39:59 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
[4/15/2015 8:39:59 AM] Using instance: DEV01, catalog: DQS.
[4/15/2015 8:39:59 AM] Executing action: Validate collation argument.
[4/15/2015 8:39:59 AM] Action 'Validate collation argument' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Check whether system reboot is pending.
[4/15/2015 8:39:59 AM] Action 'Check whether system reboot is pending' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Create data quality event source.
[4/15/2015 8:39:59 AM] Action 'Create data quality event source' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Request Database Master Key password from user..
[4/15/2015 8:41:05 AM] Action 'Request Database Master Key password from user.' finished successfully.
[4/15/2015 8:41:05 AM] Executing action: Approve removal of data quality services previous schema.
[4/15/2015 8:41:05 AM] Action 'Approve removal of data quality services previous schema' finished successfully.
[4/15/2015 8:41:05 AM] Executing action: Load Installation Scripts.
[4/15/2015 8:41:05 AM] Extracting script to: C:\Users\SqlServiceAcct\AppData\Local\Temp\3mo2vwbu.xch
[4/15/2015 8:41:06 AM] Extracting script: db\create_core_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\create_logic_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\create_transient_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\static_data.sql
[4/15/2015 8:41:06 AM] Extracting script: db\drop_dq_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: db\db_version.sql
[4/15/2015 8:41:06 AM] Extracting script: helper\DeleteSchemaDs.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\create_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_tables.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_database_properties.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\master_create.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\master_recreate.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies_tsql.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_dq_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\create_service_broker_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_service_broker_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_single_user.sql
[4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_multi_user.sql
[4/15/2015 8:41:06 AM] Extracting script: db\upgrade_all_versions.sql
[4/15/2015 8:41:06 AM] Extracting script: recreate_schema.bat
[4/15/2015 8:41:06 AM] Extracting script: upgrade_schema.bat
[4/15/2015 8:41:06 AM] Extracting script: upgrade_version_tables.bat
[4/15/2015 8:41:06 AM] Extracting script: drop_databases.cmd
[4/15/2015 8:41:06 AM] Extracting script: register_dlls.cmd
[4/15/2015 8:41:06 AM] Extracting script: unregister_dlls.cmd
[4/15/2015 8:41:06 AM] Extracting script: assembly_paths_retail.txt
[4/15/2015 8:41:06 AM] Extracting script: DQS_Data.dqs
[4/15/2015 8:41:06 AM] Extracting script: DefaultKbs.xml
[4/15/2015 8:41:06 AM] Total scripts extracted: 31
[4/15/2015 8:41:06 AM] Action 'Load Installation Scripts' finished successfully.
[4/15/2015 8:41:06 AM] Executing action: Create data quality schema.
[4/15/2015 8:41:06 AM] Script: 'recreate_schema.bat CMTSQLSVR04\DEV01 DQS SQL_Latin1_General_CP1_CI_AS'
[4/15/2015 8:41:06 AM] . Trying to connect using Windows Authentication and db name...
[4/15/2015 8:41:06 AM] Run create_databases.sql to create Data Quality Service databases if they do not exist.
[4/15/2015 8:41:07 AM]
[4/15/2015 8:41:07 AM] --> Running File: create_databases.sql
[4/15/2015 8:41:07 AM] ---[ Creating databases ]---
[4/15/2015 8:41:07 AM] Changed database context to 'master'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_dq_database.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Data Quality Databases ]---
[4/15/2015 8:41:10 AM] Creating DQS databases (DQS_MAIN, DQS_PROJECTS, DQS_STAGING_DATA)...
[4/15/2015 8:41:10 AM] Configuring DQS databases
[4/15/2015 8:41:10 AM] Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Creating Master Key for database DQS_MAIN...
[4/15/2015 8:41:10 AM] Creating Module Signing Certificate for database DQS_MAIN...
[4/15/2015 8:41:10 AM] Exporting Certificate from DQS_MAIN
[4/15/2015 8:41:10 AM] Importing Certificate into DQS_PROJECTS
[4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Creating DQS roles
[4/15/2015 8:41:10 AM] Run master_recreate.sql to recreate Data Quality Service Main and Projects Databases and drop all tables including known temporary tables.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running master_recreate.sql
[4/15/2015 8:41:10 AM] ---[ Recreate DQS Main and Projects Databases ]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_STAGING_DATA'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_all_tables.sql
[4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Symmetric Keys ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Certificates ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all FK constraints ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all views ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all tables and synonyms ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all database triggers ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all stored procedures in Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all types in Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_all_tables.sql
[4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Symmetric Keys ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Certificates ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all FK constraints ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all views ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all tables and synonyms ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all database triggers ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all stored procedures in Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all types in Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:11 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running master_create.sql
[4/15/2015 8:41:11 AM] ---[ Creating and Populating Main DQS DB ]---
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_STAGING_DATA'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: create_core_db_objects.sql
[4/15/2015 8:41:11 AM] ---[ Creating Certificates ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] ---[ Creating Symmetric Keys ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] ---[ Creating Tables ]---
[4/15/2015 8:41:11 AM] Creating Table: A_TEST
[4/15/2015 8:41:11 AM] Creating Table: A_TEST2
[4/15/2015 8:41:11 AM] Creating Table: A_FLOW
[4/15/2015 8:41:11 AM] Creating Table: A_FLOW_ANSWER
[4/15/2015 8:41:11 AM] Creating Table: A_EXECUTION_UNIT
[4/15/2015 8:41:11 AM] Creating Table: A_CODE_GROUP
[4/15/2015 8:41:11 AM] Creating Table: A_CODE_MEMBER
[4/15/2015 8:41:11 AM] Creating Table: A_CONFIGURATION
[4/15/2015 8:41:11 AM] Creating Table: A_PROCESS
[4/15/2015 8:41:11 AM] Creating Table: A_SERVICE_BROKER_TASK
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE_AUDIT
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE_ACTIVITY
[4/15/2015 8:41:11 AM] Creating Table: A_PROFILING_ACTIVITY_ARCHIVE
[4/15/2015 8:41:11 AM] Creating Table: A_CLIENT_SESSION
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_PROVIDER
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_PROVIDER_SCHEMA
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE_SUGGESTION
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE_SUGGESTION_PARSED
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_AUDIT
[4/15/2015 8:41:11 AM] Creating Table: A_IMPORTED_PROJECT
[4/15/2015 8:41:11 AM] Creating Table: A_SPELLER_DICTIONARY_VALUE
[4/15/2015 8:41:11 AM] Creating Table: A_SPECIAL_CHARACTER_RULE
[4/15/2015 8:41:11 AM] Creating Table: A_PERSISTENT_CACHE
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_OBJECTS
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_FOREIGN_KEYS
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_COLUMNS
[4/15/2015 8:41:11 AM] ---[ Creating Views ]---
[4/15/2015 8:41:11 AM] Creating View: V_A_FLOW
[4/15/2015 8:41:11 AM] Creating View: V_A_KNOWLEDGEBASE
[4/15/2015 8:41:11 AM] Creating View: V_A_KNOWLEDGEBASE_AUDIT
[4/15/2015 8:41:11 AM] Creating View: V_A_REFERENCE_DATA_PROVIDER
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: static_data.sql
[4/15/2015 8:41:11 AM] ---[ Inserting Data ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Cleansing configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Association configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert DataValueService configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Association rules configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert IndexService configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Knowledgebase configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Notification configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Interactive Cleansing configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert client paging configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert client process sampling configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Matching configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Profiling configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Process configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[FileStorageManager configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[ImportExportManager configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data Add provider]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data Add provider schema]---
[4/15/2015 8:41:11 AM] ---[Add Special characters for term normalization]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: db_version.sql
[4/15/2015 8:41:11 AM] ---[ Running version related work ]---
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_INFO
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_UPGRADE_SCRIPTS
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_UPGADE_SCRIPT_PATH
[4/15/2015 8:41:11 AM] Creating view: V_DB_VERSION
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version information]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION in PROJECTS database
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] Action 'Create data quality schema' finished successfully.
[4/15/2015 8:41:11 AM] Executing action: Register data quality assemblies and stored procedures.
[4/15/2015 8:41:11 AM] Script: 'register_dlls.cmd CMTSQLSVR04\DEV01 DQS'
[4/15/2015 8:41:12 AM] . Trying to connect using Windows Authentication and db name...
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running File: drop_all_assemblies.sql
[4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Executable Objects ]---
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Types
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Assemblies
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Schemas
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all CLR Assemblies
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop DQ startup stored procedure DQInitDQS_MAIN
[4/15/2015 8:41:12 AM] Changed database context to 'master'.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running File: drop_service_broker_objects.sql
[4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Service Broker Objects ]---
[4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:12 AM] Dropping Service Broker Services.
[4/15/2015 8:41:12 AM] Dropping Service Broker Queues.
[4/15/2015 8:41:12 AM] Dropping Service Broker Contracts.
[4/15/2015 8:41:12 AM] Dropping Service Broker Messages.
[4/15/2015 8:41:12 AM] Completed - Service Broker objects dropped.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running register_assemblies.sql
[4/15/2015 8:41:12 AM] ---[ Registering Assemblies ]---
[4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Registering Assemblies
[4/15/2015 8:41:12 AM] The following Warnings are benign to DQSInstaller and may be ignored.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] * Register .NET dependency assemblies
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.management, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'smdiagnostics, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.windows.forms, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'accessibility, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization.formatters.soap, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the
SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.jscript, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:26 AM] Warning: The Microsoft .NET Framework assembly 'system.management.instrumentation, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.messaging, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.enterpriseservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.remoting, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.framework, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.xaml, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.caching, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.utilities.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices.protocols, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web.regularexpressions, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.serviceprocess, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] * Register Microsoft.Practices assemblies
[4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.csharp, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'system.dynamic, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:47 AM]
[4/15/2015 8:41:47 AM] The preceding Warnings are benign to DQSInstaller and may be ignored.
[4/15/2015 8:41:48 AM]
[4/15/2015 8:41:48 AM] --> Running register_dq_assemblies.sql
[4/15/2015 8:41:48 AM] ---[ Registering Data Quality assemblies ]---
[4/15/2015 8:41:49 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.infra, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:50 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.core, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.dataservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.referencedata, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.index, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.associationrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:53 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.datavalueservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.domainrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.cleansing, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.association, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.flow, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:56 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.matching, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:57 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:57 AM] Resource file was not copied
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] --> Running register_assemblies_tsql.sql
[4/15/2015 8:41:57 AM] ---[ Registering Assemblies for TSQL]---
[4/15/2015 8:41:57 AM] Changed database context to 'master'.
[4/15/2015 8:41:57 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Clear the Code Member Table A_CODE_MEMBER.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] (0 rows affected)
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Clear the Code Group Table A_CODE_GROUP.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] (0 rows affected)
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Register assemblies T-SQL executable objects
[4/15/2015 8:41:57 AM] - Creating assemblies T-SQL registeration stored procedure.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Creating the internal_core schema
[4/15/2015 8:41:57 AM] - Registering Microsoft.Ssdqs.Infra T-SQL executable objects.
[4/15/2015 8:42:05 AM] - Registering Microsoft.Ssdqs.Core T-SQL executable objects.
[4/15/2015 8:42:11 AM] - Registering Microsoft.Ssdqs.DataService T-SQL executable objects.
[4/15/2015 8:42:16 AM] - Registering Microsoft.Ssdqs.ReferenceData T-SQL executable objects.
[4/15/2015 8:42:21 AM] - Registering Microsoft.Ssdqs.Index T-SQL executable objects.
[4/15/2015 8:42:26 AM] - Registering Microsoft.Ssdqs.Cleansing T-SQL executable objects.
[4/15/2015 8:42:32 AM] - Registering Microsoft.Ssdqs.Association T-SQL executable objects.
[4/15/2015 8:42:37 AM] - Registering Microsoft.Ssdqs.Flow T-SQL executable objects.
[4/15/2015 8:42:42 AM] - Registering Microsoft.Ssdqs T-SQL executable objects.
[4/15/2015 8:42:51 AM] - Registering Microsoft.Ssdqs.DataValueService T-SQL executable objects.
[4/15/2015 8:42:56 AM] - Registering Microsoft.Ssdqs.DomainRules T-SQL executable objects.
[4/15/2015 8:43:01 AM] - Registering Microsoft.Ssdqs.AssociationRules T-SQL executable objects.
[4/15/2015 8:43:06 AM] - Registering Microsoft.Ssdqs.Matching T-SQL executable objects.
[4/15/2015 8:43:12 AM] - Creating refresh assemblies stored procedure.
[4/15/2015 8:43:12 AM] Changed database context to 'master'.
[4/15/2015 8:43:12 AM] - Creating refresh assemblies helper linked server.
[4/15/2015 8:43:12 AM] - Creating and registering [dbo].[DQInitDQS_MAIN] (calls internal_core.InitServer) as startup stored procedure.
[4/15/2015 8:43:12 AM]
[4/15/2015 8:43:12 AM] --> Running File: create_service_broker_objects.sql
[4/15/2015 8:43:12 AM] ---[ Registering Service Broker Objects ]---
[4/15/2015 8:43:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:43:12 AM] - Creating SB dispatcher stored procedure, messages and contract
[4/15/2015 8:43:13 AM] - Creating parallel execution SB queues and services
[4/15/2015 8:43:13 AM] - Creating calibration SB queues and services
[4/15/2015 8:43:13 AM] - Creating parallel calibration SB queues and services
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM] Successfully registered all assemblies.
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM] Action 'Register data quality assemblies and stored procedures' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Set product version property.
[4/15/2015 8:43:13 AM] Action 'Set product version property' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Create MDS user (if MDS login exists).
[4/15/2015 8:43:13 AM] Action 'Create MDS user (if MDS login exists)' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Load out of the box data.
[4/15/2015 8:43:22 AM] Started loading knowledgebase 'DQS Data'
[4/15/2015 8:45:04 AM] Starting installation rollback...
[4/15/2015 8:45:04 AM] Installation rollback completed successfully.
[4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
to an instance of an object.
 at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
 at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
 at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
 at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
 at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
 --- End of inner exception stack trace ---
 at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
 at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
 at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
 at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
 at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.

Thank you for the quick response.
Unfortunately running cmd as admin had no effect on the result. Same exact error.
After the rollback indicated in the log above, only the DQS_STAGING_DATA database remains in the sql server instance.

The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
process could not execute 'sp_repldone/sp_replcounters' on XXXXX".
Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause.
***********Error messages from SQL Logs******
**Dump thread - spid = 0, EC = 0x0000000111534460
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error: 17066, Severity: 16, State: 1.
External dump process return code 0x20000001.
External dump process returned no errors.
Thank you in advance.

You need to determine if this error is a transient one or a show stopper one.
It sounds like your log reader agent has crashed and can't continue.
If so your best bet is to call Microsoft CSS and open a support incident.
It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

DB13 Database check getting following error

Job started
Step 001 started (program RSDBAJOB, variant &0000000000116, user ID KMDBASIS)
No application server found on database host - rsh/gateway will be used
Execute logical command BRCONNECT On host sapbwpor3
Parameters: -u / -jid CHECK20070822134120 -c -f check
BR0801I BRCONNECT 7.00 (26)
BR0252E Function NetShareGetInfo() failed for 'sapmnt' at location BrEnvProcess-89
BR0253E errno 2310: This shared resource does notexist.
BR0806I End of BRCONNECT processing: cdvzfvhd.log2007-08-22 13.41.25
BR0280I BRCONNECT time stamp: 2007-08-22 13.41.25
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished

this post is duplicated at DB13 Database check getting following error.

Error in executing Database Check on SRM Server (BRCONNECT)

Similar Messages

Maybe you are looking for