I am trying to deploy/process a cube in Visual Studio to a database on my local SQL Server.
But I get the error: "A device attached to the system is not functioning".
I have followed this solution: https://www.mattiasdesmet.be/2020/06/16/ssas-locale-error-while-processing-cube/ but I still get the error after changing Locale and LocaleName in Registry Editor for the sid for the accounts "NT Service\MSSQLServer" and "NT Service\MSSQLServerOLAPService" running my SQL Server and Analysis Services.
Are there other things I can do?
Related
This started happening to me in the past week or so. I've searched the web and tried various suggested solutions, nothing has worked so far. I didn't change my password during this time period. I tried rebooting my laptop, reconnecting to the network (VPN), running ipconfig /release & ipconfig /renew, all to no avail.
I have no problem connecting to the SQL server database running on my local machine, it's when I try to connect to a database running on a network server that this issue comes up. Outside of VS, I can connect to the network database from Management Studio without any issue.
In SQL Server Object Explorer, I tried to add a new SQL Server (my local database server appears in the list), I got the error message "The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server)"
Any helpful insight would be greatly appreciated.
When running a third party developed EXE located on the shared folder of Windows Server 2012 R2, which connects to SQL Server 2012 Express, the following error occurs:
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.
When the EXE is 'Run as Administrator' it works fine. But this application interfaces with Office and other programs, so running as administrator puts it into protected memory space that conflicts with other applications. I need it to open normally, as before.
This error has only occurred since client workstations had Windows 10 1803 and higher installed. Bizarrely, workstations that updated to 1803 and higher are unaffected. Only on new installs has the problem occurred.
There was something about 1803 which changed the network stack, client side, that caused a lot of different problems for SQL connections and I have seen a hundred different solutions but none work in our case.
Client machines connect to Server 2012 using domain login accounts. Each domain user account is given local admin rights and full administrator rights. The client workstations are normal Windows 10 Pro install with ESET antivirus. When testing the ODBC connection, it is successful and works. Only when running the program does the error occur.
On the Server side I have.... Enabled Named Pipes, Disabled and Removed SMB1.0
So what is going on here? Why from 1803 on must we run as administrator to get a connection?
Data source name not found
I would first check if the Data Source is defined below "User" or "System" .
If it is User for the Administrator there is no way to access it except if the user previously run it by using the option "Run with administrative permission"
In case it is defined as System DSN likely the user after 1803 does not have enough permission to access the registry where it is stored, so this is the most probable case scenario.
The optimal is to see if you can modify your connection using OLE or something else rather than ODBC so it can be DNSless, eventually try to define a DSN with the same name below User with the same user who is running it that should be read before the framework is going to look for the same DSN name under the system / local machine registry section.
To troubleshoot deeper registry permission issues you can use the former Sysinternals procmon downloadable from MS website, this must executed using "Run with administrative permission"
I've installed a instance of SQL Server and i select Integration Services in the setup wizard.
However, when I run SQL Server Management Studio as 'Administrator', I can see my instance under.
Database Engine
Analysis Services
Reporting Services
However, I can't see my instance under 'Integration Services'.
The service is running in Configuration Manager.
UPDATE 1
When trying to enter the server name manually it gives the following error:
the RPC server is unavailable
If you means this form:
For the first time you login you have to enter the integration services server name manually, Note that you don't have to enter the full instance name Server\Instance, you just need to enter the Server name.
Example:
If the machine name is MyPC and the SQL server instance is SQLDATA, then you should enter MyPC not MyPC\SQLDATA
UPDATE
the RPC server is unavailable
if you are sure that your account has sufficient privileges you can follow the links provided in the following MSDN answer.
The RPC Server is unavailable - Tried almost everything!
You may need to open port 135 (or whatever port SSIS is running under) in Windows Firewall on the server.
It would be good to specify the executable path (such as E:\Microsoft SQL Server\130\DTS\Binn\MsDtsSrvr.exe) as well as the specific network type that these connections should come from.
I want to connect my Windows 7 pc (Workgroup) to Server 2008R2 (domain) using hyper V.In server active directory is installed. I tried steps explained in http://community.spiceworks.com/how_to/show/30571-configuring-remote-administration-of-hyper-v-on-a-windows-7-pc .It didn't work for me.
EDIT
I am getting following error message when I tried to connect to server:
"Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."
It is quite difficult to understand what is exactly your issue as you even don't mention any error messages which, I believe, you should get upon connection attempt. But generic answer will be following:
1. Disable firewall on machine you want to manage and ensure that you have network connectivity between management workstation and managed server.
2. After connectivity is confirmed run Hyper-V management console under account with appropriate rights on target server and try to connect to your server.
As for your spcecified error message and especially for scenarious when management workstation and Hyper-V server are not in the same domain or not in trusted domains (i.e. one or both of them in workgroup) this most likely requires extra configuration step on the management workstation: you should allow ANONYMUS LOGON to DCOM on the management workstation. This is required because WMI makes calls back from the server to the client. This is entirely expected (and is not Hyper-V specific). When a server is in a workgroup, the DCOM connection from the server back to the client is "anonymous".
To acomplish this do the following on the management workstation: Run (Win+R) > dcomconfig + Enter then in opened component services window expand the tree down through Component Services > Computers > My Computer, slect My Computer, right-click, choose properties and select the COM Security tab. Click Edit Limits in the Access Permissions area. Select “ANONYMOUS LOGON” from the list of users, and make sure Remote Access/Allow is checked in the permissions area.
You also should add user account you using to manage server into "Distributed COM Users" group on Hyper-V server.
For more detailed instructions with screen shots and overview of all prerequisites for Hyper-V remote management you may refer to the series of blog posts on Hyper-V remote management by John Howard: link to part 1 of this blog posts series.
I am in the process of evaluating TFS 2010. I am trying to install onto our application server which sits in a domain and runs Windows 2008 R2 Standard.
We already have a SQL Server in place on a separate Windows 2008 box that I want to use - this is in the same domain.
After installing TFS, I am using the Advanced Configuration Wizard to try and complete the setup. There are 3 bits that are reporting errors : "Database" and "Reporting".
When I enter the SQL Server details, TFS gives me this error :
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you attempting to connect to is online, and that you have required permissions to connect... (it goes on a bit more)
The server I have installed TFS on is a web server that runs several .Net websites - all of which can connect to the SQL Server with no problem.
I have tried IP Address, machine name, instance name - all report the same error.
Has anybody been in this situation before?
EDIT : Strangely if I go to the "Reporting Server" page in the wizard and enter the SQL Server name, it connects correctly in order to get the Report Server URL and Report Manager URL. So it seems this maybe user account related?
Two things spring to mind:
You'll need to make sure the TFS service accounts have permissions on the DB server.
If Windows Firewall is on on the TFS box, switch it off for a minute or two and try again.
If that solves it, turn it back on and open the SQL ports.
HTH