Ok, found a solution (but I still don't understand why it was failing...):

- Manually installed ODBC Driver 13.1 for SQL Server on the 2nd node (SQL Server Agent...

Hi, thx for the reports.

But I've a strange error.

My parameter is working, I receive all items from our CMS.

But when I select an instance at the parameter drop down list:...

OK, it works now.

I had a shared data source caused the problem! 🙂

BL0B_EATER (9/3/2015)

---

For each connecting report ( from the main page) you will need to pass in the @servername as an “action”..

See screen shot.

This is how I passed in the servername...

It's version: 10.50.4266.0

Perry Whittle (10/8/2014)

---

You're misinterpreting the data in the tables. Whether the monitor server is on the primary or secondary instance it makes no difference.

The table msdb.dbo.log_shipping_monitor_primary on the Primary...

Thx 🙂

Thx Ken, I've used the default mail profile.

If it's not set, the errormessage will say enough to create one.

And there was no double drop table statement ... the first one...

I've modified the first post to make it more readable.

Sorry for the hard reading article, but I did my best to post it good!

Hope this edit will help you all....

7points wasted.....

Yes I know, I've tried to correct it, but it didn't helped.

I even started an topic to help me, but no solutions atm ... 🙁

Till step 8 everything is ok!

In step 9, the error popups.

I've checked my system and I've found an error in the Failover Cluster Manager.

There was a group 'Available storage' in...

USE AdventureWorks2008R2 ;

CREATE USER CustomApp WITHOUT LOGIN ;

GRANT IMPERSONATE ON USER::CustomApp TO [adventure-works\tengiz0] ;

GO

http://msdn.microsoft.com/en-us/library/ms173463.aspx

In SSMS, select your database, select 'Security', right-click 'Users' : 'New users...'

Ok, found your problem.. 🙁

You cann't select "Without login" 🙁

The error popus just after 'Validating Feature Settings'... hope this gives some more info.

I just tried to remove node on the active node: same error 🙁