thx steve, yes i always go to advanced with things like this.  in this case, in the final oledb destination, i change the data type in advanced and ssis ignores...

• This reply was modified 3 days, 1 hours ago by stan.

this gets better and better.   we see the same values on another vm's config  where there is no issue with processing full an ssas db.   we also see the problematic...

i believe this is the problem.   Does the community know what causes these values to be set to 1?   Is that perhaps the default nowadays?   I dont see them even...

• This reply was modified 3 days, 16 hours ago by stan.

tried following the instructions shown below , thru powershell, to determine if certain known registry settings might have been set but basically the error thrown was that there is no...

may have to open a ticket with MS.   will post back here what, if anything, that i find out.

thx steve, that was already done in step #2 following your recommendation.   #1 just proved that db was accessible from another client.

i'm wondering if the community has heard that there...

• This reply was modified 3 days, 20 hours ago by stan.

i tried MSOLEDBSQL (in ssas's conn string to the engine) instead of sqlncli11 but got the same error.  it might be time to bring in MS.

• This reply was modified 3 days, 20 hours ago by stan.

thx steve, these are the steps i followed and i should mention that one of our network guys says all ports are open...

1.  from ssms on my local i connected...

• This reply was modified 3 days, 21 hours ago by stan.
• This reply was modified 3 days, 20 hours ago by stan.