Warning in log after updating SQL server when installing cumulative updates
Every time I install cumulative updates for Lync 2013, when I run the command to update the SQL database which is
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLLYNPROD1.domain.local -Verbose
I get the two warnings below in the log. The update works OK and I don't have any issues. I get a warning just for this database for the database itself and the log path. Can't find anything on it searching. Any idea where to start looking
Warning: The
database rtcxds being updated has data file path at
\\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf and supplied data file path is
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf.
Supplied path will be ignored.
Warning: The
database rtcxds being updated has log file path at
\\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf and supplied data file path is
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf.
Supplied path will be ignored.
There is only one CsData folder on the Lync server but the install program is complaining about the RTCXDS database which is on our enterprise backend SQL server. The path above is correct.
\\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf for data and
\\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf for logs
but a bogus path of
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf for data and
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf for logs is being supplied from somewhere to the install program.
Fortunately, the install program knows enough to ignore the supplied path and take what it is given from SQL. Just trying to figure out where this supplied path is coming from. It could be anywhere. As I said, needle in a haystack.
Similar Messages
-
SSIS 2008 Logging - SSIS Log Provider for SQL Server
Simple SSIS package - copies a table from Server A to Server B.
Everything works except logging using SSIS Log Provider for SQL Server. Selecting the similar events to using
SSIS Log Provider for Text Files does generates a file on the server.
I specified server B on the configuration for SSIS Log Provider for SQL Server.
Logged on with a username with sysadmin rights on Server B. Executed the package using that login and nothing is written to msdb..sysssislog
any ideas what's going on or what am I doing wrong?Just to be sure that the basics are right :
You sure that you configured the log provider correctly?
Selected the required 'components' on the left bar?
Selected events on the Details Tab?
selected the right table? I mean it should be --> select * from msdb..sysssislog
The default schema in your DB setup is dbo right? Coz, if not the logging will be a real problem. You might wanna recreate the table then ..
Btw, if you still experience issues, I'd advise you to enable all events and check for logging just to make sure that there isnt any prob with the DB setup ..
Do try and let us know :)
Edited:
Also a few more:
Check what database you chose in the connection setting page of the logging configuration wizard and check for entries in sysssislog of tht DB as, the sysssislog will be created only in that db.
Ensure that you have execute permission on sp_ssis_addlogentry in that particular db (mostly msdb). Can be checked via:
select name,
has_perms_by_name(name, 'OBJECT', 'EXECUTE') as has_execute
from msdb.sys.procedures
where name like 'sp_ssis_addlogentry' --for 2008 edition and up
or name like 'sp_dts_addlogentry' --for 2005 edition
Thanks to @Sathyanarrayanans for pointing this out :)
Hope this should help ..
Thanks, Jay <If the post was helpful mark as 'Helpful and if the post answered your query, mark as 'Answered'> -
Transaction log backup through SQL Server Management studio
Dear All,
I need to configure transaction log backup through SQL server management studio.
It is already being configured for our PRO server(not by me) and now I want to configure it for DEV server.
In PRO I am taking it through(SID/right click/task/backup)
Then under backup type only full and differential option is coming for DEV.
Whereas for PRO all three(full/differential/transaction log) is coming.
Please suggest how to do it for DEV.
helpful suggestion will be duly rewarded.
Regards,
AshutoshHi,
Just go to the database you want
right click then properties then options
then set recovery model to full.
Hope this helps .
Regards,
Vamshi. -
Unable to install SCOM when SQL server is installed in other machine
Hi,
I am getting problem to install SCOM when SQL server is installed in other machine. I installed SQL server in a VM. The name of SQL server is SqlServer. When i tries to install scom in other machine i get error that SQL server could not be found. I installed
SQL server with default instance. Also my firewall is off in both the nmachineHi
do you have sysadmin rights on sql ? ensure you have sysadmin rights
to test sql connection you can use UDL test refer below link for more information
http://blogs.msdn.com/b/farukcelik/archive/2007/12/31/basics-first-udl-test.aspx
Regards
sridhar v -
Cannot Access SQL Server When Internet Down
Dear All,
I have a problem about connect to sql server.
I can't connect to sql server when my internet down.
The server in one network with my PC. I connect to the server with local IP.
Server IP 172.1.2.1 and my ip 172.1.2.25. I connect with windows Authentication.
When internet down, i can't connect to sql server using windows authentication but still work with sql server authentication.
What must i do to fix this problem?
i want connect sql server using windows authentication with or without internet connection.
Best regards,
SurbaktiHello,
If you have the Named Pipes protocol enable, you can use (local) or the dot “.” as instance name,
instead of the IP or the name of the computer.
http://technet.microsoft.com/en-us/library/ms191294.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server 2012 Install Error 17182
I am trying to install SQLSERVER 2012 SP1 (cuz my VisioStudios told me to) but the SQLEngine and Replication failed. Looking into the log I get the following:
2014-03-20 15:04:42.61 spid5s Starting up database 'msdb'.
2014-03-20 15:04:42.61 spid11s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-03-20 15:04:42.62 spid11s Error: 17182, Severity: 16, State: 1.
2014-03-20 15:04:42.62 spid11s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-03-20 15:04:42.62 spid11s Error: 17182, Severity: 16, State: 1.
2014-03-20 15:04:42.62 spid11s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-03-20 15:04:42.62 spid11s
Error: 17826, Severity: 18, State: 3.
Apparently there is something wrong with my certificate? If I run certutil -store - user I don't see any problems there
So what do I do now?
Should I just delete everything as suggested in thread "SQL Server 2012 Install Failure 17190, Severity:16, State:1"
Thank You to anyone who can give me a hand!Hi ,
According to your description, as other post, this error may be occurred due to a corrupt user profile for the account running SQL Services. You can try change the service account to a local (built-in) account which have permission to read the private key
of the SSL certificate. In addition, according to your error message, we need to examine the certificates that have been generated launching mmc.exe, for more information, see:
http://www.sqldbadiaries.com/2013/01/01/service-does-not-start-tdssniclient-initialization-failed-with-error-0x80092004-status-code-0x80/
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/8f27fbb3-1566-408a-bfde-abdde17fb424/ssl-sql-server-permission?forum=sqlsecurity
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Where are the jar files located in the server in which the MS SQL Server is installed?
Hello All,
Please tell me the place where jar files are located in the system in which the MS SQL Server is installed.
Please help me as early as possible.
Thanks in advance.
Thanks and Regards, Readers please vote for my posts if the questions i asked are helpful.Check BOL page: Using the JDBC Driver
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
How many sql server can installed in a server
how many sql server can installed in a server?????
Depends on the characteristics of the computer and the version of SQL Server.
> Product Specifications for SQL Server 2014
> Planning a SQL Server Installation
> Hardware and Software Requirements for Installing SQL Server 2014
The question is generic; could You specify?
José Diz Belo Horizonte, MG - Brasil -
Hi All,
I applied SQL server 2008 R2 SP3 recently but report builder doesn't work since then
When click on report builder gives error like 'Application validation did not succeed. Unable to continue.
and when I try to see details the error summary like following:
+File, Microsfot.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
this is urgent.
Please reply me asap.
thanks a lot in advance.
Regards,
Nik
Regards, NamanHi nikp11,
According to your description, you recently updated SQL Server 2008 R2 to SP3, Report Builder doesn’t work since then the error occurs: "Application validation did not succeed. Unable to continue".
This is an known issue in SSRS 2008 R2 SP3 that Microsoft has published an article addressing this issue. It is not planning to release a fix for this issue. But we could implement one of the following workarounds:
Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM.
Install and run Report Builder of SQL Server 2014.
Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
Reference:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch
Thank you for your understanding.
Best Regards,
Wendy Fu -
SCCM coudn't connect to database after recovering SQL server
Hello.
Please help to solve a problem. After crashing data storage, i have lost my SCCM and SQL server. I have restored SCCM server as virtual machine and re-install SQL server. I restored old databases to the new SQL server. Same instances and names.
And now i have logs smsexec.log :
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
I found that i lost my certificate
i found article Certificate drop down menu empty when trying to select SSL certificate to enable SQL Server 2008 client encryption
but i get an error when trying to execute certificate request.
ERROR TRANSLATE --- no information about certificate template
I don't know what to do. Plz help. This problem sticks me. :(~===================== << Starting Configuration Manager 2012 Setup >> =====================
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: ConfigMgr2012 Setup was started by AV\dobrokhotov.vn.
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Command line specified was: "C:\Program Files\Microsoft Configuration Manager\bin\X64\SetupWpf.exe"
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
FQDN for server SRV-SCCM is SRV-SCCM.ashipyards.com
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Target computer is a 64 bit operating system.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Phase is 1C7 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting the default CSV folder path Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: Mobile Device (INTL), LangPack: 0.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Language: RUS, Server LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: RUS, Client LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Build Number = 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Configuration Manager Version = 5.0 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Minimum Build Number = 800
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: SqlMasterDB = MSSC\master Configuration Manager Setup
01.04.2015 15:37:05 8980 (0x2314)
Removed SQL alias SRV-SQL.ashipyards.com\MSSC successfully.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\MASTER for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS Master for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\SYSTEMCENTERCM_S01 for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS ACCESS for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: 'SRV-SCCM.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Run Site Maintenance on the primary site.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:06 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Retrieving current site control image...
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
CSiteSettings::ReadActualSCFFromDatabase: Failed to get sql connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
ERROR: Failed to retrieve verifiable site control data
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Evaluating for Site Maintenance process.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: g_SetupCmdLine.bMoveSql 0, g_SetupCmdLine.sNewSqlServer , g_SetupCmdLine.sNewSqlDatabaseName , pSetupInf->SqlMasterDB MSSC\master.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
ERROR: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:51
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04. -
I was running SQL Server 2012 in Win 7 64 bit OS. Some how I found SQLSERVER server is not running and I was not able to run the service. Then I tried to unisntall and install again. And I found that some of the SQL Server
features got failed, like: Reporting Services - Native, Database Engine Services, Data Quality Services, Full-Text and Semantic Extractions for Search and SQL Server Replication. I checked the Summary.txt
file from location C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log. It thsi logs referes to another log file location like:
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, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140127_151409\sql_engine_core_inst_Cpu64_1.log
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=sql_engine_core_inst.msi%400x162A16FE%400x1639
I did unisntall/install multipel times. But fhw to fix the issue that saying in sql_engine_core_inst_Cpu64_1.log file.:
=== Verbose logging started: 1/27/2014 15:45:04 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\ScenarioEngine.exe ===
MSI (c) (C4:BC) [15:45:04:321]: Resetting cached policy values
MSI (c) (C4:BC) [15:45:04:321]: Machine policy value 'Debug' is 0
MSI (c) (C4:BC) [15:45:04:321]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (c) (C4:BC) [15:45:04:322]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (C4:BC) [15:45:04:322]: Grabbed execution mutex.
MSI (c) (C4:BC) [15:45:04:323]: Cloaking enabled.
MSI (c) (C4:BC) [15:45:04:323]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (C4:BC) [15:45:04:323]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:327]: Running installation inside multi-package transaction E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
MSI (s) (38:8C) [15:45:04:327]: Grabbed execution mutex.
MSI (s) (38:A0) [15:45:04:327]: Resetting cached policy values
MSI (s) (38:A0) [15:45:04:327]: Machine policy value 'Debug' is 0
MSI (s) (38:A0) [15:45:04:327]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (s) (38:A0) [15:45:04:452]: Machine policy value 'TransformsSecure' is 0
MSI (s) (38:A0) [15:45:04:452]: User policy value 'TransformsAtSource' is 0
MSI (s) (38:A0) [15:45:04:475]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (38:A0) [15:45:04:475]: Specified instance {18B2A97C-92C3-4AC7-BE72-F823E0BC895B} via transform :InstID01.mst;:InstName02.mst is already installed. MSINEWINSTANCE requires a new instance that is not installed.
MSI (s) (38:A0) [15:45:04:475]: MainEngineThread is returning 1639
MSI (s) (38:8C) [15:45:04:477]: User policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Machine policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (38:8C) [15:45:04:478]: Restoring environment variables
MSI (c) (C4:BC) [15:45:04:481]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C4:BC) [15:45:04:481]: MainEngineThread is returning 1639
=== Verbose logging stopped: 1/27/2014 15:45:04 ===
Please advice. I searched many places and did not get actual solution that will resolve my case.
Nusrat AkhterHi Nusrat Akhter,
According to your description, when installing the first install failed, and it looks like the instance did not uninstall completely. To solve the issue I recommend you changed the instance name in re-installing SQL Server, and check if it can work fine.
There is a similar issue that the SQL engine will not start, and there is no method of uninstalling either it, or any of the components etc. You can review the following post.
https://connect.microsoft.com/SQLServer/feedback/details/710892/sql-server-2012-rc0-install-fails-citing-invalid-drivers
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
SQL Server 2012 Installed KB2793634 and it completed successfully but display error in the event log
Hi
Running SQL Server 2012 with SP1 on Windows 7 x64 SP1
One of the machines that this is installed displayed that the Windows Installer was starting repeatedly, like every 30 secs
I installed KB2793634 and everything completed successfully. No errors in any of the Summary, Detail, etc and all check marks at the end. I went throught the event viewer and in the application log and saw the following
Product: SQL Server 2012 Database Engine Services - Update '{4023B523-7241-4B6D-83A4-92105B0A3DC8}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the
following link for instructions on turning on logging support:
Is this something with the KB. How do I find what the issue is and what do I do to fix it? Or is this a real error?
I brought up SQL Server and the issue that the KB resolves seems to been resolved. I can connect to the instance just fine, the version of the KB has been applied to the instance so now it is at 11.0.3128
Any information will be greatly appreciated.Hi,
According to the description, I know the patch that was successfully installed after the msiinstaller error.
1. Per
KB304888 and mentioned the possibility that the hotfix was launched a second time after the initial successful update.
I suspect if you have installed any hotfixes or Cumulative updates after installing Service Pack 1 for SQL Server 2012.
Reference:
http://support.microsoft.com/kb/2793634
2. Check the application log. Is the error happening intermittently?
Thanks.
Tracy Cai
TechNet Community Support -
Tansaction Log File of SQL Server
Dear Guys,
We have implemented ECC 6.0 on Windows 2003 Server / MS SQL 2005 platform. For backup purpose we have bought Tivoli. Some reason we cant backup of Database from DB13. Our Transaction log file is goin to increase, when after taking the backup of Transaction log, I shrink the log file but size of log file never decrease. So size of log file increase and free size on disk decrease. Second issue is, Can I shirnk the log file when SAP instance run ...??
So help me out in this 2 issues.
Thanks & Regards,
Charanjit Singh.Hi,
The log space is usually huge after a fresh install. You can use the following script to shrink the log file. Make sure you take a full backup of the database before you run. If you running in production system make sure you run during the scheduled downtime after a full backup.
1) BACKUP LOG <DB_NAME> TO [<DEVICE_NAME>] WITH NOFORMAT, NOINIT,
NAME = N'<DESCRIPTION>', SKIP, NOREWIND, NOUNLOAD, STATS = 10 --backup transaction log to a backup device
GO
2) USE <DB_NAME> --switch to the database
GO
3) DBCC SHRINKFILE (N'<LOGICAL_LOG_FILE_NAME>' , 2024) --shrink the file to 2gb (2024). use sp_helpdb to find out the logical file name
GO
4) sp_helpdb <SID> --view the new size
go
5) dbcc loginfo (<SID>) -- a status of 2 means transaction is dirty.
Repeat steps 1 thru 5 until log size shrinks to your desired size.
The step 3 value of "2024" is 2gb which tries to shrink the log file to 2MB. But it is not guaranteed. That is why you have to run it multiple times.
The step 5 displays output of the transactions in the log file. The status of "2" means it is dirty. If you see this value at the end of result set then there is less chance of shrinking the log file. if you see the value of "2" in the middle of the result set then there is likely chance of shrinking the file. "DBCC LOGINFO" is an undocumented command in SQL Server. But it is a favourite command of all DBAs'.
I hope this helps.
RT
Message was edited by:
R.T.
Message was edited by:
R.Th. -
SQL Server 2012 SP2 Cumulative Update 5
We are starting to take a look at Cumulative update 5 for SQL Server 2012 SP2. The Installation was going smooth until the very in, where it sat on trying to start MSSQLServer for several minutes and finally timed out. Why does Cumulative
patch 5 says it failed to start the service when the server is already running? Version number changed, and everthing looks ok, except for the error message in the log file.
Is this a valid installation or do I need to try again?
Thanks.
DJThanks for the reply. The ErrorLog is too large to post in 1 reply. Will post multiple times.
Version of the SQL Server shows 11.0.5582.0
Dj
Post 1
2015-03-24 14:13:23.82 Server Microsoft SQL Server 2012 - 11.0.5582.0 (X64)
Feb 27 2015 18:10:15
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-24 14:13:23.82 Server (c) Microsoft Corporation.
2015-03-24 14:13:23.82 Server All rights reserved.
2015-03-24 14:13:23.82 Server Server process ID is 37184.
2015-03-24 14:13:23.82 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-24 14:13:23.82 Server Authentication mode is MIXED.
2015-03-24 14:13:23.82 Server Logging SQL Server messages in file 'L:\SQL Server\Log Files\ERRORLOG'.
2015-03-24 14:13:23.82 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2015-03-24 14:13:23.82 Server Registry startup parameters:
-d H:\\System DB\Data\master.mdf
-e L:\SQL Server\Log Files\ERRORLOG
-l G:\\System DB\Logs\mastlog.ldf
2015-03-24 14:13:23.82 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2015-03-24 14:13:24.15 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2015-03-24 14:13:24.15 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 14:13:24.15 Server Detected 8191 MB of RAM. This is an informational message; no user action is required.
2015-03-24 14:13:24.15 Server Using locked pages in the memory manager.
2015-03-24 14:13:24.15 Server Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
2015-03-24 14:13:24.22 Server This instance of SQL Server last reported using a process ID of 39820 at 3/24/2015 2:09:46 PM (local) 3/24/2015 6:09:46 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 14:13:24.23 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-24 14:13:24.23 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-24 14:13:24.24 Server Software Usage Metrics is disabled.
2015-03-24 14:13:24.24 spid4s Starting up database 'master'.
2015-03-24 14:13:24.30 spid4s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 14:13:24.33 Server CLR version v4.0.30319 loaded.
2015-03-24 14:13:24.36 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 14:13:39.41 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\\System DB\Data\master.mdf] in database [master] (1). The OS file handle is 0x0000000000000598.
The offset of the latest long I/O is: 0x0000000002a000
2015-03-24 14:13:53.94 spid4s Recovery completed for database master (database ID 1) in 29 second(s) (analysis 3 ms, redo 39 ms, undo 8 ms.) This is an informational message only. No user action is required.
2015-03-24 14:13:54.19 spid4s CHECKDB for database 'master' finished without errors on 2015-03-06 08:35:22.387 (local time). This is an informational message only; no user action is required.
2015-03-24 14:13:54.19 spid4s Resource governor reconfiguration succeeded.
2015-03-24 14:13:54.19 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.19 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.21 spid4s Server name is 'Server'. This is an informational message only. No user action is required.
2015-03-24 14:13:54.22 spid4s Failed to verify Authenticode signature on DLL 'S:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
2015-03-24 14:13:54.22 spid9s Starting up database 'mssqlsystemresource'.
2015-03-24 14:13:54.22 spid14s Starting up database 'msdb'.
2015-03-24 14:13:54.23 spid15s Starting up database 'Mgmt'.
2015-03-24 14:13:54.24 spid16s Starting up database 'Web2'.
2015-03-24 14:13:54.24 spid12s The certificate [Cert Hash(sha1) "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"] was successfully loaded for encryption.
2015-03-24 14:13:54.24 spid18s Starting up database 'Web2A'.
2015-03-24 14:13:54.24 spid9s The resource database build version is 11.00.5582. This is an informational message only. No user action is required.
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv6> 1433].
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv4> 1433].
2015-03-24 14:13:54.25 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2015-03-24 14:13:54.26 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\sql\query ].
2015-03-24 14:13:54.26 Server Server is listening on [ ::1 <ipv6> 1434].
2015-03-24 14:13:54.26 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-03-24 14:13:54.26 Server Dedicated admin connection support was established for listening locally on port 1434.
2015-03-24 14:13:54.26 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This
is an informational message. No user action is required.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local ] for the SQL Server service.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local:1433 ] for the SQL Server service.
2015-03-24 14:13:54.39 spid9s Starting up database 'model'.
2015-03-24 14:13:54.42 spid4s 1 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.42 spid4s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 14:13:54.46 spid9s 1 transactions rolled forward in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.47 spid9s 0 transactions rolled back in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.62 spid9s Clearing tempdb database.
2015-03-24 14:14:17.34 spid9s Starting up database 'tempdb'.
2015-03-24 14:14:27.05 spid19s The Service Broker endpoint is in disabled or stopped state.
2015-03-24 14:14:27.06 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2015-03-24 14:14:27.07 spid19s Service Broker manager has started.
2015-03-24 14:14:27.21 spid15s CHECKDB for database 'Mgmt' finished without errors on 2014-09-14 00:02:54.637 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.58 spid16s CHECKDB for database 'Web2' finished without errors on 2015-03-22 00:00:43.253 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'ProvisionAgentIdentity.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.93 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Starting execution of dummy.sql
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Database 'master' is upgrading script 'repl_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s Executing replication upgrade scripts.
2015-03-24 14:14:27.99 spid4s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:28.07 spid4s Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 14:14:28.09 spid4s Executing sp_vupgrade_replication.
2015-03-24 14:14:28.50 spid4s Upgrading publication settings and system objects in database [Mgmt].
2015-03-24 14:14:28.89 spid4s Upgrading publication settings and system objects in database [Web2].
2015-03-24 14:14:29.98 spid4s Upgrading publication settings and system objects in database [Web2A].
2015-03-24 14:14:30.48 spid4s Could not open database [LEGACY_DSS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.52 spid4s Upgrading subscription settings and system objects in database [Mgmt].
2015-03-24 14:14:31.17 spid4s Attempting to load library 'xprepl.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:31.19 spid4s Using 'xprepl.dll' version '2011.110.5582' to execute extended stored procedure 'xp_repl_encrypt'. This is an informational message only; no user action is required.
2015-03-24 14:14:31.19 spid4s Upgrading subscription settings and system objects in database [Web2].
2015-03-24 14:14:31.75 spid4s Upgrading subscription settings and system objects in database [Web2A].
2015-03-24 14:14:32.31 spid4s Could not open database [LEGACY]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.33 spid4s Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication\ArticleResolver
2015-03-24 14:14:32.59 spid4s sp_vupgrade_replication executed successfully
2015-03-24 14:14:32.59 spid4s Saving upgrade script status to 'SOFTWARE\Microsoft\MSSQLServer\Replication\Setup'.
2015-03-24 14:14:32.59 spid4s Saved upgrade script status successfully.
2015-03-24 14:14:32.59 spid4s Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:32.92 spid4s Starting execution of PRE_MSDB.SQL
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:33.08 spid4s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:15:00.06 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\\System DB\Logs\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000790.
The offset of the latest long I/O is: 0x00000000efac00
2015-03-24 14:16:00.87 spid4s DBCC TRACEOFF 1717, server process ID (SPID) 4. This is an informational message only; no user action is required.
2015-03-24 14:16:00.87 spid4s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 14:16:00.88 spid4s
2015-03-24 14:16:00.88 spid4s Creating table temp_sysjobschedules
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysdownloadlist...
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysjobhistory...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table systargetservers...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table sysjobsteps...
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.09 spid4s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.10 spid4s DMF pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s DC pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s Check if Data collector config table exists...
2015-03-24 14:16:01.25 spid4s Data Collector state before upgrade: 0
2015-03-24 14:16:01.25 spid4s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 14:16:01.25 spid4s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 14:16:01.33 spid4s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 14:16:01.33 spid4s End of DC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s DAC pre-upgrade steps...
2015-03-24 14:16:01.33 spid4s Starting DAC pre-upgrade steps ...
2015-03-24 14:16:01.33 spid4s End of DAC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.33 spid4s Starting execution of MSDB.SQL
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.42 spid4s Checking the size of MSDB...
2015-03-24 14:16:01.60 spid4s
2015-03-24 14:16:01.60 spid4s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 14:16:01.60 spid4s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB.SQL
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Dropping view MSdatatype_mappings...
2015-03-24 14:16:01.63 spid4s Dropping view sysdatatypemappings...
2015-03-24 14:16:30.94 spid4s Dropping table MSdbms_datatype_mapping...
2015-03-24 14:16:30.95 spid4s Dropping table MSdbms_map...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms_datatype...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms...
2015-03-24 14:16:30.99 spid4s Creating table MSdbms
2015-03-24 14:16:31.00 spid4s Creating table MSdbms_datatype
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_map
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_datatype_mapping
2015-03-24 14:17:30.97 spid4s Definining default datatype mappings
2015-03-24 14:17:30.98 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 14:17:31.08 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 14:17:31.12 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 14:17:31.17 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 14:17:31.22 spid4s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 14:17:31.28 spid4s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 14:17:31.33 spid4s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 14:17:31.38 spid4s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 14:17:31.45 spid4s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 14:17:50.00 spid4s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 14:17:59.30 spid4s Creating view MSdatatype_mappings
2015-03-24 14:17:59.31 spid4s Creating view sysdatatypemappings
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_proxy_for_subsystem
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_login_for_proxy
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_mailitems_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_startup_info
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_has_server_access
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_perf_counters
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_notify
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_log_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_is_sqlagent_starting
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_job_identifiers
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_schedule_identifiers
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_jobproc_caller
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_downloaded_row_limiter
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_post_msx_operation
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_performance_condition
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_date
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_time
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_update_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_job_references
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_all_msx_jobs
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_accountparams_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_target_server_job_assignment_sql
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_server_description
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_principal_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_set_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_get_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_account_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_operator
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_add_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_defect
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_update_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_enlist
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetserver
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_enlist_tsx
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_create_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_get_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_alter_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_set_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_drop_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_update_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_help_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_admin_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_profileaccount_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_verify_category
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_update_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_value_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_resync_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_add_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_purge_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_update_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_full
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_summary
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_logmailevent_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_jobserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_start_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_stop_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_status_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_downloadlist
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_queue_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems_internal
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailMessage
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_isprohibited
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_subsystem
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailQueues
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_ProcessResponse
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_add_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_MailItemResultSets
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_attach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_process_DialogTimer
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_detach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_readrequest
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_replication_job_parameter
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_GetAttachmentData
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_RunMailQuery
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_schedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_validate_user
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_jobstep_db_username
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_send_dbmail
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_verify_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_ExternalMailQueueListener
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep_internal
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_sysmail_activate
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_write_sysjobstep_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_subplan
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_update_subplan_tsx
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_schedule_description
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_subplans_by_job
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobschedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_open_logentry
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_close_logentry
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_log
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_subplan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_delete_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_verify_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_start
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_script
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_update_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_clear_dbmaintplan_by_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_composite_job_info
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobcount
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobs_in_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_manage_jobs_by_login
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_apply_job_to_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_help_maintenance_plan
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_remove_job_from_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_job_alerts
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_start_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_stop_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_cycle_agent_errorlog
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_chunked_jobstep_params
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobsteps
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_refresh_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_jobhistory_row_limiter
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_in_sync
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_log_jobhistory
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_get_date_from_file
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_check_msx_version
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_get_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_probe_msx
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_update_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_set_local_time
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_multi_server_job_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_remove_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_target_server_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_backup
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_uniquetaskname
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_restore
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_addtask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_change_monitor_role
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_droptask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_create_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: trig_targetserver_insert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert_internal
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_addlogentry
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listpackages
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listfolders
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_alert
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletepackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_add_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_sqlagent_is_srvrolemember
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_update_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_category_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_putpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator_jobs
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_proxy_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_credential_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_addfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_notify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystems
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_renamefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_notification
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystem_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_setpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_login_identifiers
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_ssis_getpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobactivity
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sqlagent_is_member
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy_permissions
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_add_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_drop_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_get_message_description
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_proxy_to_subsystem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobhistory_sem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_login_to_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_convert_jobid_to_char
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_login_from_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_proxy_from_subsystem -
No SMTP log after upgrade to Server 4.0.3
I just updated my server to 4.0.3 and I initially had an error message saying that a script was not owned by postfix repeated in the SMTP log file.
First I tried to fix it with disk utility but it didn't work.
So in Terminal I did: sudo chown _postfix /Library/Server/Mail/Data/mta/./guid_device_maps.plist
Now I have no SMTP log showing in the server menu any ideas on how to get it back is very welcome.
Kind regards
PeterOkay I reinstalled the Server from App Store and we're back to square one with the message:
postfix/postfix-script[2941]: warning: not owned by _postfix: /Library/Server/Mail/Data/mta/./guid_device_maps.plist
However, http://topicdesk.com/faqs/os-x-server-mail-services-faq/166-what-is-virtual-mail -hosting-or-are-virtual-mail-domains say the message doesn't matter.
So I apologise for the false alarm.
Kind regards
Peter
Maybe you are looking for
-
[SOLVED] Can't get printer to work
Hi. I followed the wiki on how to set up cups and add a printer. But it's not working. Here is the result of [paco@archnme ~]$ tail -n 100 -f /var/log/cups/error_log E [06/Jun/2011:19:56:35 -0400] Unable to set ACLs on root certificate "/var/run/c
-
Trying to get started.. but fumbling badly.
I just got my first MacBook Pro on monday (currently posting from it). I decided this morning that I wanted to register a .mac name and try it out for its free trial period. I went to system settings, clicked on the .mac icon, and typed in my newly c
-
How can I get the audio to work again?
I have no audio output (external or internal) on my computer. When I click on the speaker is is in gray. When I go to sound in network preferences and go to output it only lists digital output/built-in output and is says the selected device has no ou
-
Third party extension in Jdeveloper 11.1.2.0.0
Hi All, Now Jdev 11.1.2.0.0 is supports for third party extension(PMD rules) ?. Thanks, Vass Lee.
-
10.10.3 broke my ethernet connection but not my WiFi
I usually connect to the internet on my late 2008 MacBook via Wifi, and when I need the additional speed I just plug in the ethernet cable from the router to the laptop. But following the update to 10.10.3 (and following some changes that needed to b