Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Remote SQl setup

40 views
Skip to first unread message

Chris Morgan

unread,
Jun 3, 2007, 5:35:01 PM6/3/07
to
I am about to install Beta 2 but would like to use one of our standard SQL
servers.

In the documentation provided it talks about using sqlprep.msi, but that is
about it.

Is there any other information about how to achieve this.

I dont want to be in the position of starting the install and finding that I
have made a mess of things before I even get to the fun part (how many times
have I been there before with server products).

Any additioanal information would be great.

--
Kindest Regards
Chris

Karandeep Anand [MSFT]

unread,
Jun 3, 2007, 8:30:44 PM6/3/07
to
Chris - we've seen a couple of posts in the last few days about remote SQL
installation issues. While this has been well tested, if you want, you can
wait to see how the other posts get resolved.

Thanks,
Karandeep Anand [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message
news:C7F52608-3846-4554...@microsoft.com...

Raghu Ram Vemula [MSFT]

unread,
Jun 4, 2007, 2:22:38 AM6/4/07
to
Chris,

For complete set of steps to use an existing instance, please refer to the
section on "Installing DPM V2 Beta2" in the DPM V2 Deployment guide.
On the remote SQL server instance, please ensure you have a functional,
linked install of Reporting Services - this needs IIS 6.0.

The guide, along with other important documentation can be downloaded from
here:
https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=205&DownloadID=6599

--
Thanks
Raghu Ram Vemula [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message
news:C7F52608-3846-4554...@microsoft.com...

Karandeep Anand [MSFT]

unread,
Jun 4, 2007, 3:42:55 AM6/4/07
to
Adding to my own post by stealing answer from another post from Prashant :)

There are some limitations of the remote SQL server scenario in Beta2:
1. You cannot use an instance on the local machine
2. Clustered instance is not supported

For complete set of steps to use an existing instance, please refer to the
section on "Installing DPM V2 Beta2" in the DPM V2 Deployment guide.
On the remote SQL server instance, please ensure you have a functional,
linked install of Reporting Services - this needs IIS 6.0.

The guide, along with other important documentation can be downloaded from
here:
https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=205&DownloadID=6599

Thanks,


Karandeep Anand [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Karandeep Anand [MSFT]" <karande...@online.microsoft.com> wrote in
message news:%23m74Z%23jpHH...@TK2MSFTNGP03.phx.gbl...

Chris Morgan

unread,
Jun 4, 2007, 6:08:07 PM6/4/07
to
Hi there...

I did have all the documentation and had read it before I started, but it
was not clear what was expected (what does sqlprep.msi do and where should it
be run?).

Anyway I gave it a go and things seemed to be going well, but where did the
requirement for Powershell come from, I did not see that in the doco.

Just as I was getting excited, the installed died ... I have retired a few
times, changing things on the remote DB server, but can not solve this... the
following is the last few lines from the install log...

Any ideas and I will give it another go.

One thing to think about... the install will only allow you to create the DB
on the C drive, both mdf and ldf files. That is not great as my maind file
systems are SAN/DAS based not on the main system disk. I would suggest that
you either pick up the default drives from the SQL install or allow the
person installing to select what disk to put the database files.

[6/4/2007 10:52:38 PM] Information : Creating tables
[6/4/2007 10:52:38 PM] Information : Execute the SQL script
[6/4/2007 10:52:38 PM] Data : FileName = "C:\Program Files\Microsoft Data
Protection Manager\SQL\90\Tools\Binn\SQLCMD.EXE"
[6/4/2007 10:52:38 PM] Data : Arguments = -b -E -d DPMDB -i
MiniSetupDBConfiguration.sql -r -S w3k-dbprod01
[6/4/2007 10:52:39 PM] Data : Error code = 0
[6/4/2007 10:52:39 PM] Information : Adding DPM Server entry in
tbl_AM_Server table
[6/4/2007 10:52:39 PM] Data : Database connection string = Integrated
Security=SSPI;server=w3k-dbprod01;Pooling=false;database=DPMDB;Pooling=false
[6/4/2007 10:52:39 PM] Information : Grant execute permissions on
dbo.prc_MOM_ProductionServer_Get to DPMDBReaders$W3K-DPM01
[6/4/2007 10:52:39 PM] Information : Grant execute permissions on
dbo.prc_MOM_HeartBeat_Get to DPMDBReaders$W3K-DPM01
[6/4/2007 10:52:39 PM] Information : Add job definitions
[6/4/2007 10:53:25 PM] * Exception : =>
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. ---> System.Runtime.InteropServices.COMException
(0x80080005): Server execution failed (Exception from HRESULT: 0x80080005
(CO_E_SERVER_EXEC_FAILURE))
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors(Int32 hr, tagSAFEARRAY* exceptionResult)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.JobManagerServicesProxy.AddJobDefinition(String jobDefXml)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.CoreServicesProxy.AddJobDefinition(String jobDefXml)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature 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
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.AddJobDefinition(String jobDefinitionXmlFile)
[6/4/2007 10:53:25 PM] * Exception : => The DPM database was not
created.Use Add or Remove Programs from Control Panel to remove the DPM files
and registry entries that were created during Setup. Verify that SQL Server
is properly installed and that it is running, and then run Setup
again.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException:
exception --->
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.DatabaseConfigurationException:
exception ---> System.Reflection.TargetInvocationException: Exception has
been thrown by the target of an invocation. --->
System.Runtime.InteropServices.COMException (0x80080005): Server execution
failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors(Int32 hr, tagSAFEARRAY* exceptionResult)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.JobManagerServicesProxy.AddJobDefinition(String jobDefXml)
at
Microsoft.Internal.EnterpriseStorage.Dls.Engine.CoreServicesProxy.AddJobDefinition(String jobDefXml)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature 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
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.AddJobDefinition(String jobDefinitionXmlFile)
--- End of inner exception stack trace ---
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.AddJobDefinition(String jobDefinitionXmlFile)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.PopulateDefaultJobDefinitionsInDatabase(DBConfigurationReader dbCfgReader)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.MiniSetupConfiguration.PopulateDB(Boolean upgrading, Boolean isRemoteDb, String sqlServerMachineName)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.MachineSpecificConfiguration(Boolean
existingDB, Boolean upgrading, Boolean isRemoteDb, String
sqlServerMachineName, String instanceName)
*** Mojito error was: DatabaseCreateFailed; 0; None
--- End of inner exception stack trace ---
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.MachineSpecificConfiguration(Boolean
existingDB, Boolean upgrading, Boolean isRemoteDb, String
sqlServerMachineName, String instanceName)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.Configure(Boolean
existingDB, Boolean upgrading, String databaseLocation, String
sqlServerMachineName, String instanceName, Boolean oemSetup)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.Configure()
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallDpm()
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: DatabaseCreateFailed; 0; None
[6/4/2007 10:53:30 PM] *** Error : The DPM database was not created.

Use Add or Remove Programs from Control Panel to remove the DPM files and
registry entries that were created during Setup. Verify that SQL Server is
properly installed and that it is running, and then run Setup again.

ID: 811
[6/4/2007 10:53:30 PM] 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.

--
Kindest Regards
Chris

Prashant Kumar [MSFT]

unread,
Jun 5, 2007, 4:41:09 AM6/5/07
to
Hi Chris
Thank you for your suggestion on the DB location for DPM. We will definitely
look into this - you could file this as a feature request bug on our connect
website to participate in the beta2 bug bash that's been announced - bunch
of goodies up for grabs from that :).

SQL Prep MSI needs to be run on the server hosting the SQL server instance.
It installs necessary files for allowing DPM to work correctly with the
remote instance

Are there any event log entries in the app event log at the time of the
setup failure? Please let us know.

Thanks,
Prashant

--
--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message

news:D5CCC198-50DE-475F...@microsoft.com...

Chris Morgan

unread,
Jun 5, 2007, 5:17:01 AM6/5/07
to
Prashant,

On the Db server there are 6 errors with the following message

>>Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.1.195.111]

and on the DPM server I get 6 of the following error

>>Unable to connect to the DPM database because of a general database failure. Make sure that Microsoft SQL Server is running and that it is configured correctly.

So I guess it is something that is trying to execute from the DPM server to
the SQl server but is not passing the correct credentials.

Is there anything else I can check/report to you.

--
Kindest Regards
Chris

Prashant Kumar [MSFT]

unread,
Jun 6, 2007, 6:31:24 AM6/6/07
to
Hi Chris,
Can you also let us know the accounts configured on the SQL server you are
using? If it is a domain user account, our setup should detect that and ask
you to enable named pipes on the machine. Did DPM setup ask for this and
have you enabled named pipes + restarted the SQL server service as required?

Thanks,
Prashant

--
--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.
"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message

news:3FE62EC9-A689-4B33...@microsoft.com...

Chris Morgan

unread,
Jun 6, 2007, 6:34:02 PM6/6/07
to
Prashant,

Any news on my access issue... I really would like to get DPM working, but
at the same time dont really want to have move more copy of SQL to maintain
if at all possible.

--
Kindest Regards
Chris

Prashant Kumar [MSFT]

unread,
Jun 7, 2007, 8:31:39 AM6/7/07
to
Hi Chris,
Reposting my earlier message... please check and revert to me if this worked
for you.

<<
Hi Chris,
Can you also let us know the accounts configured on the SQL server you are
using? If it is a domain user account, our setup should detect that and ask
you to enable named pipes on the machine. Did DPM setup ask for this and
have you enabled named pipes + restarted the SQL server service as required?

Thanks,
Prashant
>>

--
--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.
"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message

news:4B03CF00-6995-4141...@microsoft.com...

Chris Morgan

unread,
Jun 8, 2007, 5:01:01 AM6/8/07
to
Prashant

I think messages are not getting through to me... maybe I should logoff once
in a while and not just leave IE running for weeks on end and lock my machine.

The account I was using was the domain administrator account (not an account
with domain admin rights, but the proper domain admin account). I was not
sure and as the doco is not complete yet, I thought it best to use an account
that would have no problems doing anything.

I was not prompted about Named Pipes, so have now enabled it and restarted
SQL Server...

I have just tried a reinstall and had the same problem... on the SQL Server
machine in the Event Log I had 6 messages

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.1.195.111]

Sorry that I dont have better news.

Kindest Regards
Chris

Prashant Kumar [MSFT]

unread,
Jun 9, 2007, 9:16:59 AM6/9/07
to
Thanks for the update Chris.
There have been some recent glitches in viewing the posts for other
customers as well from our technet website. I apologize for the trouble.
Anyhow, since we are now getting through, here's a guess on where might the
problem lie:
DPM engine service runs under the LocalSystem account and tries to talk to
the SQL Server. SQL Server authenticates the machine on the network using
the domain controller - which seems to be denying the log on or identify the
DPM server as an anonymous log on. It might boil down to some security
setting on your Active Directory domain. Sorry for being a little vague
here - but let me know if this rings a bell...

For proceeding, in addition to the event log entries you are seeing below,
do you have any additional event logs at the same time as the issue from
Kerberos?
Please check the app and the system event logs.

Regards,
Prashant

--
--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.
"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message

news:15536C04-1A6B-4057...@microsoft.com...

Chris Morgan

unread,
Jun 9, 2007, 4:29:00 PM6/9/07
to
Prashant,

You gave me a clue... we have had a problem with certificates for some time
after we had a domain controller die a couple of years ago, it was also a
Cert Authority as well... But as we didn't really have a need to replace it
or fix the issue (and it didn't break anything) we left it alone (rather than
kill our whole AD setup).

So I looked into it again to day and found a few random entires in AD which
I cleaned up...

I then recieved the following on the PDC...

There are multiple accounts with name
MSSQLSvc/w3k-dbprod01.dataliberation.com:1433 of type
DS_SERVICE_PRINCIPAL_NAME.

I corrected this this with ADSIEdit ....

And guess what, the next install worked....

I am not sure how you connect from DPM to the SQL server, but it must be
unusual, not that I am saying it is wrong, but we only develop SQL DB systems
and have not a problem in the past 2 years....

So enough from me... thank you very much for all your help... and now I am
off to format 1.5TB and have a really good play with your program....

Thanks again

Karandeep Anand [MSFT]

unread,
Jun 9, 2007, 5:13:29 PM6/9/07
to
Chris - thanks for updating us! Good to know that you are unblocked now.
Looking forward to more feedback on DPM from you!

Thanks,
Karandeep Anand [MSFT]


This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Morgan" <Chr...@newsgroups.nospam> wrote in message

news:CB7EB623-7F63-45FA...@microsoft.com...

0 new messages