SQL Server Management 6.5.1.0 and 6.5.4.0 does not discovery SQL 2008 databases on Windows 2003

SQL Server Management 6.5.1.0 and 6.5.4.0 does not discovery SQL 2008 databases on a custom instance name or when multiple SQL instances are installed on Windows 2003.
OS Version: Windows 2203 x64 with SP2
Database Version: 10.3.5869.0
The instance in this case: I01 is running on port 49168.
SQL Server Network Configuration | Protocols for I01 | IP Addresses | IPAll | TCP Port = 49168
The DB Engine class is discovered but not the "Tcp Port" property.
The database discovery script then fails as it is missing the 8th parameter; The Port.
Looking at the discovery script DiscoverSQL2008DBEngineDiscovery.vbs i see the following WMI query.
Set oWMI = GetObject("winmgmts:\\" & computerName & "\root\Microsoft\SqlServer\" & SQL_WMI_NAMESPACE)
Set oQuery = oWMI.ExecQuery("SELECT * FROM ServerNetworkProtocolProperty
Using WMI Explorer if I connect to namespace: root\Microsoft\SqlServer\ComputerManagement10
and query "SELECT * FROM ServerNetworkProtocolProperty". There are no instances.
What am I missing or doing wrong?
Closely related to this article. https://gallery.technet.microsoft.com/Hotfix-Management-Pack-SQL-17cf1118#content.
Thanks
Gavin

Hi,
I would like to know is there any update about the issue. If the issue is solved, will you please share the resolution here to help others in this forum who encounter similar issue.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Similar Messages

SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege. I have a SQL server 2012 instance whose Agent service is configured to run
under an AD user account named 'SQLServices'. The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'. The jobs are set up to execute SSIS packages which read and
write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server). The jobs are currently executing without error and are reading writing data correctly. Upon close examination, it turns out the
SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server. How are these jobs working? I verified in profiler that the login name indeed is 'SqlServices'. I also verified
that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected. According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
some cases where that is not necessarily the case. So this is not so concerning. What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does.
The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access. What am I missing here? Any input would be helpful.

After 2 days on this forum I found the answer to my own question. In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed. This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
role. This is the login that Agent uses to connect to the local instance of SQL server. If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

Entity Framework doesn't create the database in SQL Server Management 2012, instead it just creates in (localdb)\v11.0 How to fix it?

Hi, I'm Begginer in Entity Framework. Then I'm having some problems.
I created my entities and I give Save Changes. (Ok)
Then, I Tried to Connect with the database through Server Explorer, if I use the instance of the SQL Server Management Studio 2012(PC-PAULO\INSTANCIAPJ) as Server Name, the database doesn't appears but, if I use the the instance (localdb)\v11.0 the dabase
appears.
How to change the save to the SQL Server Management Studio 2012, I don't know where this (localDB)\v11.0 saves.
Help-me Thank you :D

Hello PauloJos,
The code should be ok and it is really strange that the database is only created into the local database in your machine. I am wondering if it is related with the machine environment, could you please have a try with below demo on your machine which works
on my side and if it is possible, please have a try to run your application on other machines to see if it works:
class Program
static void Main(string[] args)
#region https://social.msdn.microsoft.com/Forums/en-US/00eff3c4-2336-4807-9212-e6f2a6c8812e/entity-framework-doesnt-create-the-database-in-sql-server-management-2012-instead-it-just-creates?forum=adodotnetentityframework
using (CFDbContext db = new CFDbContext())
db.Database.CreateIfNotExists();
#endregion
public class CFDbContext : DbContext
public CFDbContext() : base("UltraFoda3") { }
public DbSet<TestOne> TestOnes { get; set; }
public class TestOne
public int ID { get; set; }
public string Name { get; set; }
Config file is similar:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>

<section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</configSections>
<entityFramework>
<defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework">
<parameters>
<parameter value="v11.0" />
</parameters>
</defaultConnectionFactory>
<providers>
<provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
</providers>
</entityFramework>
<connectionStrings>
<add name="UltraFoda3" connectionString="Data Source=YourServer;Initial Catalog=UltraFoda3;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
</connectionStrings>
</configuration>
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

Your Client Does not Support Opening this list with Windows Explorer on Windows Server 2012 R2

I am trying to open a document library in Internet Explorer 11 on a Windows 2012 R2 server and I am receiving Your Client Does not Support Opening this list with Windows Explorer

Hi,
According to your post, my understanding is that you wanted to open a document library with the Internet Explorer 11 on a Windows 2012 R2 server. But you received the following error message: Your client
does not support opening this list with Windows Explorer.
There can be multiple reasons for it.
So, I recommend you can check with the following steps:
Go to the “Server Manager” of “Administrative Tools” > Enable the “Desktop Experience” feature in your environment.
Go to the “Services” of “Administrative Tools” >
Ensure the “WebClient” service is started.
Ensure that your computer has supported Web browser.
Ensure that Internet Explorer is configured correctly to add
https://*.sharepoint.com to Local intranet site in the “Security Tab” of “Internet Options”.
Ensure that
you have applied the latest updates on the system.
For more information, you can refer to the following articles:
http://blogs.technet.com/b/asiasupp/archive/2011/06/13/error-message-quot-your-client-does-not-support-opening-this-list-with-windows-explorer-quot-when-you-try-to-quot-open-with-explorer-quot-on-a-sharepoint-document-library-in-office-365-site.aspx
http://mcgeeky.blogspot.com/2010/02/your-client-does-not-support-opening.html
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

SQL Server Management Studio and Native Client different behaviour on delete

I have a problem with transaction containing insert and delete to same table and some select/insert/update to some other tables. Problematic table has primary key defined as combination of column1 and column2.
When two different instances using Native Client execute simultaneously this code and make inserts to table then delete part of code causes deadlock. However this doesn't happen when trying this situation in MS SQL Server Management Studio query.
Is there some option that is missing from Native Client connection string which can cause this different behaviour?

Hello,
I don't think there is a difference in the behavior. SSMS uses ADO.NET and that Provider base on the Native Client.
The difference will be more that way, when the transaction is commited and so the locks released. I guess your application keeps the transaction (much) longer open; you should commit a transaction as soon as possible to avoid long time locks and so
deadlocks.
Olaf Helper
[ Blog] [ Xing] [ MVP]

I am trying connect to a SQL instance for our CRM program and I am receiving To Connect to this Server you must use SQL Management Studio or SQL Server Management

I am trying connect to a SQL instance for our CRM program and I am receiving To Connect to this Server you must use SQL Management Studio or SQL Server Management
This is a Brand new Server 2012 that is running our CRM product and it is trying to connect to a Server 2008 R2 server with SQL Server 2008 R2 SP2 instance (10.50.4000)
I have seen this in the past where it needed the 2005 backwards compatibility components installed but those are not supported on 2012 server and this is not a 2005 SQL instance.
I am trying to install the Shared Management Objects for SQL Server 2008 but it tells me I need to install the CLR types, which I did install. But it continues to tell me to install the CLR types.
Has anyone ran into any issues like this? (this happens trying to connect to multiple SQL Servers from this new 2012 Server)
Thanks!
-Max

Hello,
Which version and edition of the SQL Server instance did you installed on the new server machine? If you install SQL Server 2012 Express edition, you can try to install SQL Server Management Studio 2012 from
this link.
You can connect to SQL Server 2008 R2 or earily verions with SSMS 2012.
What's more, Microsoft SQL Server 2008 Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0, Microsoft SQL Server Native Client, and Microsoft SQL Server System CLR Types. You can try to download and install
SQL Serve 2008 Feature Pack
which contains packages above.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL 2008 R2: Microsoft SQL Server Management Studio cannot shut down because a modal dialog is active. Close the active dialog and try again

When starting SQL Server 2008 R2 it hangs , and I cannot exit...so when trying to logoff to reset I get the following "Microsoft SQL Server Management Studio cannot shut down because a modal dialog is active. Close the active dialog and try again"Any
ideas?

Big edit...
I have 2008 R2 SP2 installed on my Windows 7 Machine which is also fully updated. The marked answer above is clearly not the solution.
The fix I had posted before did not work. It appeared to work temporarily, but now I am back to the same invisible dialogue. I have not been able to identify any pattern by which this is triggered. I can have an entire day without this
issue and then it appears the next.
The invisible modal dialogue is definitely the connection dialogue. The only way out is to hit the escape key to close it, but then I am no better off without an ability to connect to a server. The dialogue is still invisible when I re-open it.
However, even as I type this post, I have just gotten the dialogue to appear after restarting Management Studio, hitting escape, then clicking connect again. That same pattern failed just minutes ago numerous times. Again, I can't find any pattern.
See you in the clock tower.

SQL Server Management Studio has stopped working when changing fonts and colors

I installed sql server management studio 2012 about 3 months ago to test drive and from time to time I'll attempt to change my background color of the TSql editor "In the fonts and colors option under tools"; however, the entire studio crashes
and restarts.
This has been ongoing since I first installed it 3 or 4 months ago, and have waited on posting to a fourm for help, assuming I am not the only one this is happening to I've waited for an update that might fix the issue.
I've got to start on some heavy scripting and that god awful white background kills my eyes. I've got to have a black background or my work day is cut off by about 3 hours becuase of strain.
What can I provide to someone that would help me with this?
Thank you,
Erik
Specialize in software for the construction industry.

Hello,
Could you please apply the following updates and let us know the results?
http://www.microsoft.com/en-us/download/details.aspx?id=35575
http://support.microsoft.com/kb/2790947
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to install SQL Server Management Studio 2012

Hi ,
I was trying to install MS SQL Server Manager on Server 2012 R2 and I was facing an issue while doing so.
Please find the attached screenshot for the same.
Need help ASAP.
Thanks

Hi Mahesh,
Could you please install the Microsoft Windows Software Development Kit (SDK) as dave’s post? Below is the download link for the latest release of SDK.
https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Unable to Login SQL server management studio:sql server 2005

Hello All,
I am unbale to login SQL server management studio with below scanario:
Server Type:Database Engine
Server Name:XXX
Authntication:Windows Auth
After enter "Connect : button below eeror is displaying
Error:"Canot connetc to XXX server
Additional information:
Attempted to read or write protected memory .This is an often an indication that the other memory is corrupt(System.Data)
Note:Database is connecting R3trans return code 0000
SAP is working fine
Please provide suggestion and inpuits its very urgent
Thanks
Nekkalapu

HI All,
Issue resolved after rebooting the server.
Thanks
Nekkalapu

How to change Font Size of Object Explorer in "SQL Server Management Studio"

Dear Team,
"SQL Server Management Studio" is a fantastic IDE for the database.
There are so many customization options available but one thing many users missing is that " How to change Font Size of Object Explorer?"
Can you please accumulate this feature in IDE ASAP?
Many Thanks,
Bhavesh

Its there
Go to Tools -> Options
Then under Environment you've fonts and colors tab where you can specify a higher font size.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Not able to access database from a remote machine using SQL Server Management Studio

Hi,
I have a DB_BOX with SQL Server 2008 R2 installed. I can access the databases on the local machine using SQL Server Management Studio but it is not accessible from other machines, though the machines are in same domain.
I have remote enabled on SQL Server box, TCP enabled, firewall off. I checked with IP Address too, all SQL Server services are running.
The SQL Server log shows the message
The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.
I get the below message in SSMS from remote machine.
Details of error message are
===================================
Cannot connect to DB_BOX.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
Server Name: DB_BOX
Error Number: 64
Severity: 20
State: 0
Program Location:
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Sorry, missed the message from the errorlog in the original post. You shouldn't have included that big .Net dump that hid the important facts. :-)
My first Google attempt on that message (which I have never seen before) suggests that the TCP Enpoint is stopped, so try this:
ALTER ENDPOINT [TSQL Default TCP]
STATE=STARTED;
Erland Sommarskog, SQL Server MVP, [email protected]
This solves the problem. Thanks...

How to create a database in Sql server management studio

how to create a database in Sql server management studio

One method is to run the SQL statement below from a SSMS query window:
CREATE DATABASE MyDatabase;
You can also right-click on the Databases node in SSMS Object explorer and select New Database.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Verify that SQL Server Reporting Services is installed properly and that it is running.

I am trying to install DPM 2010 on Windows 2008 R2. Running through installation and the server that I'm installing DPM to will also host the SQL instance and Reporting instance. Pretty much choosing all the defaults.
Installation gets to reporting portion and fails. It says that I need to verify that Reporting Services is running.   The exact error is:
Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)
Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
It is running and working, I can go to the URL and see Reports installed.   It grabbed a server certificate which is valid and binds that to 443. I have tried this as well with the certificate removed.
Here is the relative portion of the DPM 2010 log:
[6/25/2010 10:30:01 AM] * Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException: Exception of
type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
[6/25/2010 10:30:01 AM] * Exception : => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception --->
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
*** Mojito error was: ReportDeploymentFailed; 0; None
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.ConfigureReporting(Boolean isRemoteDb)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[6/25/2010 10:30:07 AM] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
[6/25/2010 10:30:07 AM] Information : Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components
copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)

Hello,
The real problem is the error UnableToConfigureAccount and *** Mojito error was: PasswordTooShort; 0; None
The reason is due to the new password complexity on Windows 2008 which states the following:
Password must meet complexity requirements
This security setting determines whether passwords must meet complexity requirements.
If this policy is enabled, passwords must meet the following minimum requirements:
Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
Be at least six characters in length Contain characters from three of the following four categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Non-alphabetic characters (for example, !, $, #, %)
Complexity requirements are enforced when passwords are changed or created.
Default:
Enabled on domain controllers.
Disabled on stand-alone servers.
Note: By default, member computers follow the configuration of their domain controllers.
Please use a more secure password adhering to the above criteria and DPM should install fine.
Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

SQL Server Management 6.5.1.0 and 6.5.4.0 does not discovery SQL 2008 databases on Windows 2003

Similar Messages

Maybe you are looking for