Usuário com melhor resposta
Erro ao iniciar o SQL Management Studio SQL Server 2008 R2 Microsoft SQL Management Studio package failed to load

Pergunta
-
Boa tarde amigos.
Semana passada fui instalar o SQL Server 2008 R2 e pela primeira vez obtive esse erro ao iniciar o Management Studio.
Logo ao carregar o management studio aparece a mensagem : Microsoft SQL Management Studio package failed to load. E o Management Studio fecha.
Eu já desinstalei, reinstalei...em alguns fóruns pediram para entrar no regedit e apagar um registro e tudo isso foi em vão.
Gostaria de compartilhar o log para, se souberem da solução, compartilhá-la em nosso fórum.
2013-08-13 16:22:35.20 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2013-08-13 16:22:35.20 Server (c) Microsoft Corporation.
2013-08-13 16:22:35.20 Server All rights reserved.
2013-08-13 16:22:35.20 Server Server process ID is 6700.
2013-08-13 16:22:35.20 Server System Manufacturer: 'POSITIVO', System Model: 'POS-MIH61CF'.
2013-08-13 16:22:35.20 Server Authentication mode is WINDOWS-ONLY.
2013-08-13 16:22:35.20 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-08-13 16:22:35.20 Server This instance of SQL Server last reported using a process ID of 2952 at 13/08/2013 16:22:29 (local) 13/08/2013 19:22:29 (UTC). This is an informational message only; no user action is required.
2013-08-13 16:22:35.20 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
2013-08-13 16:22:35.21 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-08-13 16:22:35.21 Server Detected 4 CPUs. This is an informational message; no user action is required.
2013-08-13 16:22:35.24 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-08-13 16:22:35.26 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-08-13 16:22:35.28 spid7s Starting up database 'master'.
2013-08-13 16:22:35.33 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-08-13 16:22:35.38 spid7s Resource governor reconfiguration succeeded.
2013-08-13 16:22:35.38 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-08-13 16:22:35.38 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-08-13 16:22:35.38 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-08-13 16:22:35.39 spid7s SQL Trace ID 1 was started by login "sa".
2013-08-13 16:22:35.39 spid7s Starting up database 'mssqlsystemresource'.
2013-08-13 16:22:35.42 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2013-08-13 16:22:36.00 spid10s Starting up database 'model'.
2013-08-13 16:22:36.01 spid7s Server name is 'USUARIO-CLEBER'. This is an informational message only. No user action is required.
2013-08-13 16:22:36.10 spid10s Clearing tempdb database.
2013-08-13 16:22:36.15 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2013-08-13 16:22:36.16 spid13s Starting up database 'msdb'.
2013-08-13 16:22:36.16 spid14s Starting up database 'ReportServer'.
2013-08-13 16:22:36.16 spid15s Starting up database 'ReportServerTempDB'.
2013-08-13 16:22:36.24 Server A self-generated certificate was successfully loaded for encryption.
2013-08-13 16:22:36.24 Server Server is listening on [ 'any' <ipv6> 1433].
2013-08-13 16:22:36.25 Server Server is listening on [ 'any' <ipv4> 1433].
2013-08-13 16:22:36.25 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2013-08-13 16:22:36.25 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2013-08-13 16:22:36.25 Server Server is listening on [ ::1 <ipv6> 1434].
2013-08-13 16:22:36.26 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2013-08-13 16:22:36.26 Server Dedicated admin connection support was established for listening locally on port 1434.
2013-08-13 16:22:36.26 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. 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-08-13 16:22:36.26 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-08-13 16:22:36.33 spid10s Starting up database 'tempdb'.
2013-08-13 16:22:36.39 spid15s The Service Broker protocol transport is disabled or not configured.
2013-08-13 16:22:36.39 spid15s The Database Mirroring protocol transport is disabled or not configured.
2013-08-13 16:22:36.40 spid15s Service Broker manager has started.
2013-08-13 16:22:36.77 spid7s Recovery is complete. This is an informational message only. No user action is required.
Fico no aguardo, pois é urgente.
terça-feira, 13 de agosto de 2013 19:35
Respostas
-
Olá amigos. Como resolução para esse problema, formatei a máquina. Logo após a instalação, precisei dar umas permissões a pasta DTS e COM e rodou perfeito.
Valew pela ajuda
- Marcado como Resposta Célio.Pereira terça-feira, 20 de agosto de 2013 20:14
terça-feira, 20 de agosto de 2013 20:14
Todas as Respostas
-
Célio,
O que você postou é o errorlog do SQL Server, você não encontrará logs da ferramenta neste. Tente encontrar algum erro relacionado no Event Viewer.
Dê uma olhada também nas respostas desse tópico. http://social.msdn.microsoft.com/Forums/sqlserver/pt-BR/239e10b9-4dda-4912-a0e0-c4ed9de23f98/erro-package-microsoft-sql-management-studio-package-failed-to-load
terça-feira, 13 de agosto de 2013 19:45 -
Onde consigo esse log? Pois é uma máquina windows 7 64 bit e não um server.
Desculpe a minha ignorância, mas isso nunca aconteceu.
=(
terça-feira, 13 de agosto de 2013 19:58 -
O Event Viewer (Visualizador de Eventos) pode ser acessado procurando pelo nome junto ao menu iniciar ou pelo Run (Executar) -> eventvwr.exe
Na tela que abrir você navega no canto superior esquerdo -> Visualizador de Eventos -> Logs do Windows -> Aplicativo ou Sistema, veja se encontra algo aqui relacionado ao erro do SSMS.
http://www.tecmundo.com.br/windows-7/3334-dicas-do-windows-7-conheca-o-visualizador-de-eventos.htm
terça-feira, 13 de agosto de 2013 20:13 -
log da instalação:
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2013-08-14 13:43:06
End time: 2013-08-14 13:54:50
Requested action: Install
Machine Properties:
Machine name: USUARIO-CLEBER
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: Português (Brasil)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: AUTORIDADE NT\SERVIÇO DE REDE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: AUTORIDADE NT\SERVIÇO DE REDE
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: USUARIO-CLEBER\usuario
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130814_134205\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: AUTORIDADE NT\SERVIÇO DE REDE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: USUARIO-CLEBER\usuario
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130814_134205\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130814_134205\SystemConfigurationCheck_Report.htm
quarta-feira, 14 de agosto de 2013 17:00 -
Olá amigos. Como resolução para esse problema, formatei a máquina. Logo após a instalação, precisei dar umas permissões a pasta DTS e COM e rodou perfeito.
Valew pela ajuda
- Marcado como Resposta Célio.Pereira terça-feira, 20 de agosto de 2013 20:14
terça-feira, 20 de agosto de 2013 20:14