Jump to content


marlonc1980

Error updating sccm 2012 sp1

Recommended Posts

Hi all, I have passed the requirements, I have installed sql sp2 2008r, all goes well, when installing I get the following screen, is a primary site, is working well, no problems, but when I want to update this message and I can not access the previous console for obvious reasons

 

DATOS EN LOG

 

 

ERROR: SQL Server error: [42000][156][Microsoft]
[sql Server]Incorrect syntax near the keyword 'to'.  $$<Configuration Manager Setup><01-25-2013 14:16:37.084+300><thread=3756 (0xEAC)>
INFO: Executing SQL Server command: < ~ DECLARE @viewname nvarchar(255) ~ DECLARE newviews INSENSITIVE CURSOR FOR ~ SELECT name FROM sysobjects WHERE type='V' AND name like 'v[_]%' ~ OPEN newviews ~ FETCH NEXT FROM newviews INTO @viewname ~ WHILE (@@FETCH_STATUS = 0) ~ BEGIN ~ EXEC('GRANT SELECT ON ' + @viewname + ' to smsschm_users') ~ FETCH NEXT FROM newviews INTO @viewname ~ END ~ CLOSE newviews ~ DEALLOCATE newviews ~ ~> $$<Configuration Manager Setup><01-25-2013 14:16:37.084+300><thread=3756 (0xEAC)>
ERROR: Failed to execute SQL Server command: ~ DECLARE @viewname nvarchar(255) ~ DECLARE newviews INSENSITIVE CURSOR FOR ~ SELECT name FROM sysobjects WHERE type='V' AND name like 'v[_]%' ~ OPEN newviews ~ FETCH NEXT FROM newviews INTO @viewname ~ WHILE (@@FETCH_STATUS = 0) ~ BEGIN ~ EXEC('GRANT SELECT ON ' + @viewname + ' to smsschm_users') ~ FETCH NEXT FROM newviews INTO @viewname ~ END ~ CLOSE newviews ~ DEALLOCATE newviews ~ ~ $$<Configuration Manager Setup><01-25-2013 14:16:37.084+300><thread=3756 (0xEAC)>
~~===================== Failed Configuration Manager 2012 Server Setup - Upgrade ===================== $$<Configuration Manager Setup><01-25-2013 14:16:37.100+300><thread=3756 (0xEAC)>

post-17189-0-02780900-1359141896_thumb.png

Share this post


Link to post
Share on other sites

I commented that the installation be half or damaged, damaged the primary site, the SMS service and I get this screen, after that I restored to a previous state, and I can access the site fine, and I can get into the console, but I have a problem with the replication, this is not running and my database is functional, there is no problem.

 

Log SQL: In theory the trust relationship in the domain is well

__________________________________

 

 

2013-01-28
16:08:04.15 Server Microsoft SQL
Server 2008 R2 (SP2) - 10.50.4000.0 (X64)



Jun 28 2012 08:36:30



Copyright © Microsoft
Corporation



Standard Edition (64-bit) on
Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)



 



2013-01-28
16:08:04.21 Server © Microsoft
Corporation.



2013-01-28
16:08:04.21 Server All rights
reserved.



2013-01-28
16:08:04.21 Server Server process ID
is 1824.



2013-01-28
16:08:04.22 Server System
Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.



2013-01-28
16:08:04.29 Server Authentication
mode is WINDOWS-ONLY.



2013-01-28
16:08:04.29 Server Logging SQL
Server messages in file 'C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.



2013-01-28
16:08:04.32 Server This instance of
SQL Server last reported using a process ID of 1824 at 1/22/2013 12:28:21 AM
(local) 1/22/2013 5:28:21 AM (UTC). This is an informational message only; no
user action is required.



2013-01-28
16:08:04.32 Server Registry startup
parameters:



-d C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf



-e C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG



-l C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf



-T 8295



-T 4199



2013-01-28
16:08:04.50 Server SQL Server is
starting at normal priority base (=7). This is an informational message only.
No user action is required.



2013-01-28
16:08:04.50 Server Detected 4 CPUs.
This is an informational message; no user action is required.



2013-01-28
16:08:05.37 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.



2013-01-28
16:08:07.35 Server Node
configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask:
0x000000000000000f:0. This message provides a description of the NUMA
configuration for this computer. This is an informational message only. No user
action is required.



2013-01-28
16:08:08.00 spid7s Starting up
database 'master'.



2013-01-28
16:08:09.66 spid7s FILESTREAM:
effective level = 0, configured level = 0, file system access share name =
'MSSQLSERVER'.



2013-01-28
16:08:10.22 spid7s SQL Trace ID 1
was started by login "sa".



2013-01-28
16:08:10.30 spid7s Starting up
database 'mssqlsystemresource'.



2013-01-28
16:08:10.41 spid7s The resource
database build version is 10.50.4000. This is an informational message only. No
user action is required.



2013-01-28
16:08:10.97 spid10s Starting up
database 'model'.



2013-01-28
16:08:10.98 spid7s Server name is
'server'. This is an informational message only. No user action is required.



2013-01-28
16:08:11.35 spid10s Clearing tempdb
database.



2013-01-28
16:08:11.78 Server The certificate
[Cert Hash(sha1) "1A2E6CFFFA87BBCE772C3B85658CE296B60018AA"] was
successfully loaded for encryption.



2013-01-28
16:08:11.84 Server Server is
listening on [ 'any' <ipv6> 1433].



2013-01-28
16:08:11.85 Server Server is
listening on [ 'any' <ipv4> 1433].



2013-01-28
16:08:11.85 Server Server local
connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].



2013-01-28
16:08:11.85 Server Server named pipe
provider is ready to accept connection on [ \\.\pipe\sql\query ].



2013-01-28
16:08:11.87 Server Server is
listening on [ ::1 <ipv6> 1434].



2013-01-28
16:08:11.87 Server Server is
listening on [ 127.0.0.1 <ipv4> 1434].



2013-01-28
16:08:11.87 Server Dedicated admin
connection support was established for listening locally on port 1434.



2013-01-28
16:08:11.92 Server The SQL Server
Network Interface library could not register the Service Principal Name (SPN)
for the SQL Server service. Error: 0x2098, state: 15. Failure to register an
SPN may cause integrated authentication to fall back to NTLM instead of
Kerberos. This is an informational message. Further action is only required if
Kerberos authentication is required by authentication policies.



2013-01-28
16:08:11.92 Server SQL Server is now
ready for client connections. This is an informational message; no user action
is required.



2013-01-28
16:08:12.40 spid10s Starting up
database 'tempdb'.



2013-01-28
16:08:12.99 spid13s Server is
listening on [ 'any' <ipv6> 4022].



2013-01-28
16:08:12.99 spid13s Server is
listening on [ 'any' <ipv4> 4022].



2013-01-28
16:08:13.07 spid13s The Service
Broker protocol transport is now listening for connections.



2013-01-28
16:08:13.09 spid13s The Database
Mirroring protocol transport is disabled or not configured.



2013-01-28
16:08:13.42 spid13s Service Broker
manager has started.



2013-01-28
16:08:24.90 Logon Error: 18456,
Severity: 14, State: 38.



2013-01-28
16:08:24.90 Logon Login failed for
user MY DOMAIN\SQL_Admin'. Reason: Failed to open the explicitly specified
database. [CLIENT: <local machine>]



2013-01-28
16:08:27.25 Logon Error: 18456,
Severity: 14, State: 38.



2013-01-28
16:08:27.25 Logon Login failed for
user MY DOMAIN\SQL_Admin'. Reason: Failed to open the explicitly specified
database. [CLIENT: <local machine>]



2013-01-28
16:08:32.86 Logon Error: 18456,
Severity: 14, State: 38.



2013-01-28
16:08:32.86 Logon Login failed for
user MY DOMAIN\SQL_Admin'. Reason: Failed to open the explicitly specified
database. [CLIENT: <local machine>]



2013-01-28
16:08:35.46 spid14s A new instance of
the full-text filter daemon host process has been successfully started.



2013-01-28
16:08:35.95 spid14s Starting up
database 'msdb'.



2013-01-28
16:08:35.95 spid17s Starting up
database 'ReportServer'.



2013-01-28
16:08:35.96 spid18s Starting up database
'ReportServerTempDB'.



2013-01-28
16:08:35.96 spid19s Starting up
database DataBase.



2013-01-28
16:08:35.96 spid20s Starting up
database 'TmpRep'.



2013-01-28
16:08:38.87 spid19s 64 transactions
rolled forward in database DataBase (7). This is an informational message only.
No user action is required.



2013-01-28
16:08:39.68 spid19s 0 transactions
rolled back in database DataBase (7). This is an informational message only. No
user action is required.



2013-01-28
16:08:39.68 spid19s Recovery is
writing a checkpoint in database DataBase (7). This is an informational message
only. No user action is required.



2013-01-28
16:08:39.78 spid52 Attempting to
load library 'xpsqlbot.dll' into memory. This is an informational message only.
No user action is required.



2013-01-28
16:08:39.89 spid52 Using
'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure
'xp_qv'. This is an informational message only; no user action is required.



2013-01-28
16:08:41.12 spid52 Attempting to
load library 'xpstar.dll' into memory. This is an informational message only.
No user action is required.



2013-01-28
16:08:41.16 spid19s Recovery
completed for database database (database ID 7) in 2 second(s) (analysis 79 ms,
redo 112 ms, undo 714 ms.) This is an informational message only. No user
action is required.



2013-01-28
16:08:41.39 spid7s Recovery is
complete. This is an informational message only. No user action is required.



2013-01-28
16:08:41.42 spid52 Using
'xpstar.dll' version '2009.100.1600' to execute extended stored procedure
'xp_instance_regread'. This is an informational message only; no user action is
required.



2013-01-28
16:08:42.05 spid52 Attempting to
load library 'xplog70.dll' into memory. This is an informational message only.
No user action is required.



2013-01-28
16:08:42.15 spid52 Using
'xplog70.dll' version '2009.100.1600' to execute extended stored procedure
'xp_msver'. This is an informational message only; no user action is required.



2013-01-28
16:09:24.59 spid89 Common language
runtime (CLR) functionality initialized using CLR version v2.0.50727 from
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.



2013-01-28
16:09:26.81 spid89 AppDomain 2
(CM_NAP.dbo[runtime].1) created.



2013-01-28
16:09:35.28 Logon Error: 17806,
Severity: 20, State: 14.



2013-01-28
16:09:35.28 Logon SSPI handshake
failed with error code 0x8009030c, state 14 while establishing a connection
with integrated security; the connection has been closed. Reason:
AcceptSecurityContext failed. The Windows error code indicates the cause of
failure. [CLIENT: SecundarySite].



2013-01-28 16:09:35.29 Logon Error: 18452, Severity: 14, State: 1.



2013-01-28
16:09:35.29 Logon Login failed. The
login is from an untrusted domain and cannot be used with Windows
authentication. [CLIENT: SecundarySite]

post-17189-0-67170900-1359414659_thumb.png

post-17189-0-64648400-1359415169_thumb.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.