Connecting to an external SSAS cube in SSDT 2012 on Windows Server 2008 R2 Core

Good Evening,
We are experiencing issues when executing an SSIS package from a SQL Server job. However, when we execute the package locally, it is
successful. The package connects to an external SSAS cube using MDX. I have attached the error message below. The connection manager is OLE DB Provider for Analysis Services 11.0. We can successfully ping the external site where the cube is located from the
server with the job.
We are using Windows Server 2008 R2 Core. We are trying to access an external cube through HTTPS by sending a username/password in the connection string. This is sent through an OLE DB connection in SSIS. I found an article which says that "Because
there is no Web browser, you cannot activate a Server Core installation or access the Internet through a firewall that requires users to log on." Does anyone have any additional details on this...is this a futile effort?
Thanks - Brett

Hi Brett,
According to your description, you are experiencing the error when you connect to SQL Server Analysis Services database on a SSIS package, right?
In your scenario, you said that the package can be executed successfully on your local environment, the issue only occurs on the SSAS server. So please ensure that the provider was installed on the server. Besides, here is a blog which describe how
to configure the Analysis Services Processing Task in SQL Server 2012 Integration Services， please refer to the link below to see the details.
http://www.mssqltips.com/sqlservertip/2994/configuring-the-analysis-services-processing-task-in-sql-server-2012-integration-services/
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

Cannot connect to SERVER. Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error 18456) - SQL Server 2012 on Windows Server 2008 R2

I've seen multiple blogs and forums with similar problems and SQL 2012 or 2008. But no solutions that work for me.
I have installed SQL Server in mixed mode (SQL and Windows authentication). I can create new Login accounts in either mode. However, I cannot get an AD security group Login account to work. I am trying to add group 'DOMAIN\Domain Admins' or 'SERVER\Administrators'
as a Login so that any of the domain's administrator accounts can open SQL Server Management Studio and act as an 'sa' account on this server.
I have deleted the SQL account 'DOMAIN\Domain Admins'.
I have restarted SQL.
I have restarted the Win2K8r2 server.
I have launched SSMS as Administrator from the desktop of SERVER.
I have launched SSMS as another user (and used 'DOMAIN\user' to lauch it) from the desktop of SERVER.
I can create a login account named 'DOMAIN\user' (who happens to be a member of the 'DOMAIN\Domain Admins' group) and give this account 'sa' security, and when I do that, this account works as expected...
How do I add a security group as a Login account and give all members of that group the ability to be an 'sa' account?

Hi geoperkins,
Are you getting the following error message?
Error: 18456, Severity: 14, State: 11
Login failed for user <Domain\user>. Reason: Token-based server access validation failed with an infrastructure error.
If that is the case, the issue could be due to that the Windows login has no profile or that permissions could not be checked due to UAC. Please disable UAC firstly and check if it is successful to log in SQL Server.
Another reason could be that the domain controller could not be reached. You may need to resort to re-creating the login. Create a new group in AD, add users to the new group, then add the group to the local admin group and create login for the group in SQL
Server.
There is a connect item describing similar issue for your reference.
https://connect.microsoft.com/SQLServer/feedback/details/680705/cant-login-to-sql-using-windows-authentication-when-user-is-in-a-domain-security-group
For more details about above error, please review the following blog.
http://sqlblogcasts.com/blogs/simons/archive/2011/02/01/solution-login-failed-for-user-x-reason-token-based-server-access-validation-failed-and-error-18456.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Windows Server 2008 Standard: Multiple Concerns: Inconsistent group policy update on client PC's, frequent disconnections of map drives and remote connection

Hi this is my first time to ask a question here in this community.
I am a system administrator here at my work and we are having some issues on some servers that we handle. Network in our office is stable and we have determined it is not a problem on the connection.
First issue - One of our domain controller consistently drops out on our Directory Server and saying it's unavailable.
Second issue - Unable to ping hostname but IP address works fine. (Sometimes hostname is ok but very intermittent)
Third issue - Since connection is unstable map drives causes to disconnect
If someone can provide any assistance on this matter it would be a great help. If screenshots needed for proper assistance would be appreciative.
Just to add that this only happen after a power failure last April of this month and a few weeks bluescreen started to show. It is a hazy version wasn't able to get any code that may lead to a hardware failure.
Now our main RDC.local is also affected so we are trying to isolate this issue and exhauted my brain since we cannot determine what causes it. Need external assistance just to give us a lead on where we can get this resolved.

Hi Ryan,
Before going further, would you please let me confirm something more? Thanks for your understanding.
1. For first issue, would you please let me know OS edition information of the problematic DC? Was it Windows Server 2008 R2 or Windows Server 2012 or any other?
à
One of our domain controller consistently drops out on our Directory Server and saying it's unavailable.
Would you please let me know the complete error message or provide a screenshot of it?
(Please hide all protected or private information.) Meanwhile, please log on the problematic DC and check if find relevant events or errors in Event Viewer.
2. For the second issue, it seems to be a DNS issue. Did you run
ipconfig /flushdns and ipconfig /registerdns command? Any find? Meanwhile, please use
ipconfig /all to display full TCP/IP configuration and check. Or you can post the
ipconfig result here. It may help us to go further analyze. By the way, would you please let me know error message that you can get when be unable to ping via hostname?
3.
àSince connection is unstable map drives causes to disconnect
May be a cause.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Problems with RDP/RDC from Mac OSX to Windows Server 2008 on External IP

We have a customer that is using Mac and Microsoft's RDC for Mac to their servers.
They've just upgraded from Windows Server 2003 to 2008 and can't connect through RDP to their TS server on external IP.
Their servers is not in any domain and it work for them to connect to another Windows Server 2008 that is located in their office when they use internal IP.
The problem is that when using RDC to the external IP they get bellow:
"Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if:
The remote computer is running a version of Windows that is earlier than Windows Vista.
The remote computer is configured to support only the RDP security layer.
Contact your network administrator or the owner of the remote computer for assistance."
From here they can choose "Connect" as they did on the Server 2003 but now they get: "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.Try reconnecting to the Windows-based computer, or contact our administrator."
and is only able to choose "Ok".
I've changed the settings on the "configuration for host server for remote desktop sessions" under General from "RDP-Security Layer" to "Negotiate" and in this case I get a logon windows where i type in all my information click logon. Here I get another
error message which says something like: (We get it in Swedish). "Connection to the windows-based computer broke since there was a problem associated with the licensificationprotocol... Try to connect again" Where I can choose "Cansel" or "reconect"
but it just keeps poping up if i chose reconnect.
I've tried all settings in the TS server and there is not much to change on the RDP client. We have installed the server certificate on the Mac client but it didn't help.
We've also tried with CoRD and it works fine as RDP from a normal Windows based computer.
The only solution I've found on google is to use CoRD instead but we got problems with that connection since it keep crasching on our computer.
In my eyes the problem is on the security requirements that the RDC for Mac needs but I can't find any inforamtion on MS sites about it.
Greatfull for all tips and trix!

I too was having the problem same as everyone else. However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security
layer is negotiate and the certificate is the one selected on that screen. It was not licensing related.
The certificate had expired and I didn't believe I needed it. But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers)
do not have IIS installed, I was a bit stumped on how to create a new certificate request. I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template
chosen was "legacy key", and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client. Neither the official 2.1.1 client or the 2.1.2 download.
The Terminal Server system event log was showing the following two errors, 36874 and 36888. The first one contained the best details and said: "An TLS 1.0 connection request was received from a remote client application, but none of the cipher suites
supported by the client application are supported by the server. The SSL connection request has failed." Upon searching the internet for that, I found this page which described the legacy key problem:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/3a2d2eec-000d-432a-abd7-6b965268c671
So, my solution most familiar to me was to use IIS and create the SSL certificate request, process that with my 3rd party CA, export the certificate with private key and then import that certificate into all of my terminal servers. Then using the session
host configuration tool, pick the new certificate and the problem was now solved.

Windows Server 2008 R2 Standard "Certificate Authority Service" / Exchange Server 2010 EMC not starting and no AD connectivity for authentication.

Hello,
I am a new IT Manager at this company and need assistance big time. Their environment looks as follows:
Server 1. Domain Controller Server (Windows Server 2008 R2 Standard) running active directory.
Server 2. Email Server (Windows Server 2008 R2 Standard) running Exchange Server 2010 .
* Note. No back ups to work with aside from whats mentioned below.
DC had a virus infection causing a lot of issues on the shared network drives 2 days ago locking up all the files with a crypto ransom virus. Running Avast suppressed the infection. Had to recover the file shares which luckily had a back up.
The issue is that the Exchange Server 2 post this lost connectivity with the AD Server 1. Exchange Server 2 when launching EMC could not launch the console stating the following:
"No Exchange servers are available in any Active Directory sites. You can’t connect to remote
Powershell on a computer that only has the Management Tools role installed."
Shortly after I found that it is possible the EMC launcher was corrupt and needed to be reinstalled following another blog post. I deleted the exchange management console.msc per instructions only to discover I couldnt relaunch it because there was
no way how. So I copied another msc file that happened to be on the DC Server 1 back to Exchange Server 2 and got it to launch again.
Another post said that it might be an issue with the Domain Account for the Computer, so to delete it in the AD Server 1 only to find that rejoining it from Exchange Server 2 using Computer>Properties> Chage Settings > Change is greyed out because
it is using the Certificate Authority Service.
I tried manually re-adding the computer in AD and modeling permissions after another server in group settings but no go. After this I was unable to login to the Exchange Server 2 with domain accounts but only local admin, receiving the following Alert:
"The Trust Relationship between this workstation and primary domain failed."
I tried running the Power Shell tools on Exchange Server 2 to rejoing and to reset passwords for domain accounts as noted in some other blogs but no luck as the Server 2 could not make the connection with Server1 or other errors it kept spitting out.
I also during the investigation found the DNS settings were all altered on both the Server 1 and Server 2 which I luckily was able to change back to original because of inventorying it in the beginning when I started.
I need help figuring out if I need to rejoin the Exchange Server 2 manually by disabling the Certificate Authority Service (or removing the CA as listed here:
https://social.technet.microsoft.com/Forums/exchange/en-US/fb23deab-0a12-410d-946c-517d5aea7fae/windows-server-2008-r2-with-certificate-authority-service-to-rejoin-domain?forum=winserversecurity
and getting exchange server to launch again. (Mind you I am relatively fresh to server managing) Please help E-Mail has been down for a whole day now!
Marty

I recommend that you open a ticket with Microsoft Support before you break things more.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Connect SQL Server 2012 from Windows Server 2003 with native client 9.0

Hi,
I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
Now I have the requirement to upgrade the SQL server from 2005 to 2012.
My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
Thanking you in advance!

Hi Soumya,
Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
Regards,
Mike Yin
TechNet Community Support

"Failed to connect to the service manager" when I try to add nodes to a cluster on Windows Server 2008 R2

Hello,
I get the following error message everytime I try to add a node to an existing cluster "Failed to connect to the service manager".
I'm running Windows Server 2008 R2,
Any ideas?

Hi saeedawadx,
Please run the cluster validation and post the error or warning information, in normal scenario the “Failed to connect to the service manager” issue often caused by the firewall
or AV soft block the others node connect, please try to disable the firewall and AV soft then try again.
The following related article will give more helpful tips,
The case of the server who couldn’t join a cluster – operation returned because the timeout period expired
http://blogs.technet.com/b/roplatforms/archive/2010/04/28/the-case-of-the-server-who-couldn-t-join-a-cluster-operation-returned-because-the-timeout-period-expired.aspx
Trouble Connecting to Cluster Nodes? Check WMI!
http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to get clients connected in WMS on windows server 2008 with c# coding

Sorry to bother anyone about this question.
Can anyone knows how to retrieve amount of client connection to Windows Media Server in real time same as WMS does on server console by c# programming ?
I got logfiles of WMS in system32 directory for details but it must be off-line of all connections which will able to get those informations for doing anything,but in this case I want real time client connection
at online when a client connects to WMS that I will get amout of that client also.
I have tried to search Windows Media Service SDK to develop this on my Windows 7 OS,but I did not find that really.
Can anyone knows this,please ?
Regards,
BigBerm

Hi SYaGCi,
Denis is right this is actually documented in the Supported Platforms Documentation:
"Windows 7 and Windows Server 2008 R2 are new platform support additions in Service Pack 3 which are only available for support on the SP3 full release install of SAP BusinessObjects Enterprise. The SP3 patch only release of SAP BusinessObjects Enterprise does not provide support for these two new platforms."
Kind regards,
John

Windows 7 64-bit Pro not connecting to SQL Server on domain Windows Server 2008 R2 Standard

I am upgrading computers from Windows XP Professional to Windows 7 Professional but I have a problem getting one of the stock control software programs we use to connect to our SQL Windows Server 2008 R2 Standard from the new Windows 7 computers.
Our computers are connected to a domain and so is the SQL Server. The Windows XP computers allows each standard domain user to log on and connect to the SQL Server via the stock control software program.
But on the Windows 7 Pro computers standard domain users can't connect to the SQL Server but the domain administrator accounts on the same Windows 7 Pro computers can connect to the SQL Server via the stock control program.
I have setup the server alias, server name and port number via the SQL Server Client Network Utility (cliconfg.exe) so I know this isn't the problem as it works when I am logged on as domain administrator.
It seems to be something to do with domain user permissions and Windows 7 Pro. There seems to be a change from Windows XP Pro to Windows 7 Pro that doesn't allow standard domain users to connect to an SQL Server. But I can't find anything about this and
can't workout how to fix it except to make all the users domain administrators which is obviously not a good thing to do. So basically I I think I need to create a group policy that allows the users to connect to the SQL Server but I have no experience doing
this and don't know where to begin.
Thanks for all you guys help and I hope someone can provide me with the solution to this problem.

Hi,
Was there any message?
Please run the stock control software as Administrator to check if it was caused by UAC.
If it could run as administrator, please add the standard domain user to local administrator.
Karen Hu
TechNet Community Support

Can I use Remote Desktop Connection (windows server 2008) even if no user is logged in?

I'm configuring a Server, running Windows Server 2008, to be accessed remotely. Suppose no user is logged in in the server (if it was just turned
on, for instance). Can I use the "Remote Desktop Connection" feature to log in remotely in this case? Or is it always necessary to have a user locally logged in, to remotely log in to one of the users available?

If its a fresh installation, RDM might not work at first.
1. You need to check firewall and allow Remote Desktop. To be specific, communication to port 3389 TCP
2. Right click My Computer --> Properties --> Remote tab
Enable Remote Desktop
Allow connections to this computer
Click users and grant the permissions for the users. By default, Administrators do have the permission. An also, the users who are members of the 'Remote Desktop Users' security group also have the permission

Sybase ODBC Connection Issue in Windows Server 2008 R2

Hi ,
We have three sybase odbc connection in Windows Server 2008 R2 server . One connection is not working now, it was working fine before 30 days.
I can ping the server address successfully from BO Server through "dsedit".
i have created the same connection in a diffrent server (Win server 2003),and it is working fine.
Sybase ASE Driver version 3.50.00.10
Please help me to overcome this issue.
Thanks,
Saurabh upadhyay

Hi Saurabh,
The error message you are reporting is telling us that you are using the very old ctlibrary ODBC Driver.
That is pretty much the only way you can get that error.
Run from a command prompt, isql -v that will return a version string. We can then verify the version.
However, the old ODBC driver will function with the newer client.
The old driver would read the sql.ini for the network address, and was also a translation layer between
the client application and the ASE.
Both were eliminated when Sybase released the "Native" ODBC Driver.
The ct_connect error states that the connection attempt is using ctlibrary.
In your ODBC configuration, Check to see in the ODBC Administrator and check to make
sure that the driver you are using for your DSN is the Adaptive Server Enterprise and not the
Sybase ASE ODBC Driver.
Also check the Drivers tab in the ODBC Admin. See what the actual file is listed for the driver.
sysybnt.dll
syodase.dll are unsupported drivers.
It would be to your advantage to open an incident with SAP for more complete support
Thank you,
Kevin

8.8 Client cannot connect to Windows Server 2008 error -1102

SAP Business On 8.8 on PL 18
This is not the first time I have had this issue with Windows Server 2008.
however everytime the resolution was diffrent. Now this site is causing trouble.
The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
The client on the Server itself can log on. It is the cleints that cannot.
I checked these below.
1 SQL Native client is installed and ok.
2. Licence server is configured and ok
3. The user has admin access to locl PC
4. The SAP user name and password are correct ( client on server can connect fine )
5. The ports 1433, 30000 and 30001 are open on the server.
6. Through SQL server configuration the named pipes and TCP are enabled.
7. SQL server browser is running
The only things I have not tried are
The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
Do you have any other ideas please ?

I have got this working but I am not confidant of the outcome - yet - I really need your expert advise here.
This is what I did. In that order.
1.     As Owen suggested I checked if there was a specified Port for the instance. What I found was TCP Dynamic ports were enabled ( SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified. Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance I set it up so the Dynamic port does not happen and manually specified the Port 1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now. Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
3.     I had to do the above step for all PCs to get them working.
4. Currently the firewall is on and clients can connect
So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off - to say its safe ?
However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things.
I would still like to get to the bottom of this to understand what is happening.
I have a SAP message running too and will ask them this same question.

OS 10.7, SMB Connection, Change to Unicode with Extended Security on Windows Server 2008 Standard

Hi All, I've searched Google, and I've also contacted Apple Support with no luck: I want to implement unicode with extended security on Windows Server 2008 Standard server shared folders so that Lion can connect normally (i.e. Finder->Go->Connect to Server->IP Address or server name) to SMB shares and access files. I'm lacking information; has anyone actually implemented unicode with extended security? If so, how?
Thanks in advance.
Tom

Thanks for the reply aorlich. Do you mean enable file sharing on my Mac? With file sharing enabled, I still cannot get to my Windows 7 shares, although the files on my Mac do become available to Windows. Thanks again.

ExFat External Hard Drive showing up as RAW on Server 2008

Correct me if I'm wrong but doesn't Server 2008 support ExFat? I plugged an external HD to a 2008 box and it can't read it and it shows up as RAW on disk
management. I plugged it into a Server 2008 R2 and it was readable. The size of the external HD is 3TB.

Hi Gary_Leung1,
Both Windows Vista with SP1 or later and Windows Server 2008 support exFAT with removable storage devices. Please try to assigned a drive letter to your disk if it now come
online please run the chkdsk /f on this disk then monitor this issue again.
More information:
Adding Hard Disk Drives
https://msdn.microsoft.com/en-us/library/dd163551.aspx?f=255&MSPPError=-2147217396
[MS-FSA]: File System Algorithms
https://msdn.microsoft.com/en-us/library/ff469524.aspx
Configuring Disks and Storage
https://technet.microsoft.com/en-us/library/ee344823%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How can I speed up logins using MacBooks to a Windows Server 2008 environment. Logging onto the network is extremely slow. We are using a wireless connection to the network in classrooms

I work in an Education environment with Windows Server 2008. I am trying to join our Macbooks to Active Directory. They are joined but the login is extremely slow. I read that this is because of a possible problem with an OS update.

Check the ethernet link speed when connected directly to the TC.. if you are plugged into the modem direct.. and comparing that with wireless on the TC we have no way of knowing where the issue is.
There is some issue related by someone when the TC was bridged.
It is extremely hard to impossible to know what is causing wireless slow down.. needs lots more info.
What is the link speed?
Set manually and try different channels.
The series 1 cannot do 2.4ghz and 5ghz simultaneously but test on 5ghz and see what the speed is like. You will need to be in the same room as the TC.

Connecting to an external SSAS cube in SSDT 2012 on Windows Server 2008 R2 Core

Similar Messages

Maybe you are looking for