recently in the server that i work with, the security team made a Hardening, after that the reporting services gives this error whenever someone (including administrators) try to access de site:
Description of the error
It's important to mention that the service run under a Domain account, for a week after the hardening the server runs smoothly but for some reason now shows this error.
We searched a lot and give the permissions to the Domain user and network service under de directories C:\Windows\Microsoft.NET , C:\Program files\Microsoft SQL Server\XXX\Reporting Services\Report server
But nothing seams to work. The error keeps the same. We also tried adding this users to the group "Distibuited COM Users" as it was in an answer in another question here.
I will appreciate the help because i am running out of ideas of what access i should grant.
The server has windows server 2012 and reporting services 2014.
Related
I know this question has been asked many times, but none of the symptoms seem to match my problem and thus none of the solutions work.
I am in the process of moving a DNN site (v. 7.04) from our company's IT infrastructure to an externally hosted VM as they were unable to give guaranteed up time. (The last straw was when their DNS server fell over Friday afternoon and we couldn't even contact anyone until Monday morning. Still took them two more days to fix it, but I digress...)
I'm administering the VM so I have full access to it and the software running on it. I do not have access to the server on which the website and database are currently running.
I have copied the website files from the old server to the new and have been provided with database backups which I have successfully restored on the new VM. The new VM is running IIS 8.5, SQL Express 2014 and Windows Server 2012 R2 Datacenter. I have set up the website in IIS and given read/write permissions to NETWORK SERVICE and IIS_IUSRS. The web.config file can be read as if I type something silly I get a syntax error showing the correct line.
Now here is where things diverge from the trivial (for me at least). I can connect to the database (on the local machine) using Management Studio, HeidiSQL and the Data Link Properties dialog (see https://www.sophos.com/en-us/support/knowledgebase/65525.aspx). All three of those work fine. When I put the connection string into the web.config, I get the can't connect error. The precise message is "DNN Error Connection To The Database Failed".
Here's the connection string I'm using, it's nothing special and is what the production server is currently using, though with a different data source of course:
Data Source=[machine]\[instance];Initial Catalog=[database]; User ID=[user];Password=[password];
I'm guessing it's not the database itself since that seems to be fine and I can connect to it as mentioned, so I'm thinking maybe something in IIS?
Any help would be appreciated.
I'm a newbie to SQL Server 2012. Here is my condition.
I have a running SQL Server 2012 Business Intelligence SP1. The problem is I cannot deploy a project to my SSAS from another computer.
The error is:
The project could not be deployed to the 'DATABASE-SERVER\MSSQLSERVER' server because of the following connectivity problems : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
The following is the things that I've tried:
Check the target name on Project > Properties > Deployment > Target server.
Check the server service --> all SQL Server services are running.
The project can be deployed from server.
The connection to server is clear
I can connect to the Database Engine and Analysis Service from another computer from SQL Server Management Studio.
Please help me to fix this problem, I've been search for many days for this problem.
Thank you, sorry for my bad english.
Best regards, Stella.
I had the same problem, for me the solution was to explicitly specify login information on the Impersonation Information tab on the Data Source.
I know this is an old thread, but I had the same issue and I reckon more will run into this buzz saw.
My problem was that the remote installation of SSAS did not have an Inbound firewall rule for SSAS application; msmdsrv.exe.
Resolution:
Log on to the server running SSAS as Administrator
Launch Windows Firewall and advanced Security
Add Inbound Rule, give it a meaningful name like SQL Server - SSAS
Action: Allow the connection
On Program and Services Tab: For 'This Program' use Browse and identify msmdsrv.exe
For SQL Server 2014, it is by default here:
%ProgramFiles%\Microsoft SQL Server\MSAS12.SQLSVR14\OLAP\bin\msmdsrv.exe
(Very similar for 2012 and 2016, the numbers are different)
Click OK; You should see a green dot with check mark
Try your project again; It should connect, did for me.
NOTE: If this also work for you, consider going back to the Inbound Rule and consider adding connection restrictions for security reasons.
I solved mine by right clicking my data source (under Data Sources in Solution Explorer) → Edit in the General tab → In Connection Manager, do two things:
Change Server name from localhost to your computer name
Use SQL Server Authentication as Authentication, as opposed to Windows Authentication, and proceed to enter your user name and password (the "sa" password you use for SSMS).
This is 2nd day I'm spending on this sql server problem! long story short, I have downloaded/installed sql server 2014 express version on my windows 8.1 operating system. sql server works fine however when I get in it and create tables or etc, when I run asp.net (mvc 4) and click on login page or register page it throws following error:
error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
I have searched in stackoveflow and also msdn, few other forums but did not find a specific and solution to nail this down.
on my machine I have:
SQL SERVER (MSSQLSERVER) service running (Automatic)
Microsoft LocalDB is installed
However,
SQL Server Browser stopped
SQL Server Agent stopped
every time I am trying to restart or start them I get this message:
The service cannot be started, either because it is disabled or because it has no enabled device associated with it[0x80070422]
I also tried this solution but it didn't help. please see this URL
http://www.aspneter.com/2013/08/error-50-local-database-runtime-error-occurred/
Can this be something in web.config?
any help will be appreciated greatly.
Thanks.
amit
Ok the problem is resolved by downloading Microsoft SQL Server 2012 SP1 Feature Pack.
Service Pack SP1
Sorry in advance... trying to get my feet wet with win 8, IIS8 Express that comes bundled with win8, Visual Studio 2012 and SQL Server 2012. I just installed all over the weekend. For the SQL Server, I mostly just accepted the defaults and "Add Current User" with an INSTANCE1
In my Visual Studio dev mode, my asp.net app connects to INSTANCE1 like this:
server=.\INSTANCE1;Database=MyDatabaseName;Integrated Security=True;Persist Security Info=False
But when I publish it out to IIS 8, it does not connect.
I've tried regiis ...I've tried NetworkService for the IIS Application Pool identity value... and lots of different connection string combinations, trial and error, but nothing seems to connect to the Instance1 - is there something that I'm not configuring correctly?
Any links or tips to troubleshoot this is greatly appreciated!
This took me hours to figure out. But hopefully it cuts down on someone else's time. You can install all of the defaults as described above, but you have to add the NT Authority\Network Service object of the database's Security|Users (I chose the global top level)...and then go in and mess with the permissions of that new user object...give it all of the necessary rights: in short, I gave it the Server Role of SysAdmin (checkbox). Thank you to those who helped me think about the problem in different ways!
Okay, these are the errors I can't backtrace at all. So I was hoping you had any idea.
When I recently rebooted my server (The server is a home computer, and just runs Windows 7 as a development machine) with Sharepoint 2010, a whole list of problems occurred.
The major error was that when I deployed my Visual Studio 2010 project, it couldn't activate my Feature. This happens more often, because I sometimes mess up in my Feature Activation event handler. But, when that happens, I can access the site, and debug the error while activating the feature manually.
However, this time, things were different. My site didn't even want to start up? So I checked IIS Manager, and it said that the site was stopped. Manually starting it resulted in the following error:
The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
I have no clue what that could mean? What file? The web.config? I really don't know.
But I saw that the Sharepoint Central Administration was running, so I decided to check there. However, this resulted in even more errors, well, there was one, but it really frightened me:
Cannot connect to the configuration database.
So, not only my Web server is having errors, but also my database server. Time to check the event logs is what I thought.
And there I'm a bit stunned. There are so many errors, I don't even know where to start. I'm just going to copy the ones which I think are important.
Unknown SQL Exception -1 occurred. Additional error information from SQL Server is included below.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Sharepoint Foundation seems to give me that one.
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://*:80/ for site 908852174. The site has been disabled. The data field contains the error number.
IIS-W3SVC seems to give me that one.
I.. really have no clue what could be the case. Since I cannot acces Central Administration, I can't check for any health issues either.
Anyone has even the slightest idea? I didn't do anything funny I believe. I was thinking that it could've been the updates that were installed, but the only updates installed were:
Security Update for Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package (KB973923)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.855.0)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.1040.0)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.1148.0)
So, it really couldn't have been that. I'm out of ideas, and I really would like to solve this.
Thanks,
Mats
EDIT: Okay, manually started up the SQL Service, and now Central Administration works. But, The Health reporting site started scaring me. There's a list of 8 items requiring my attention.
NT AUTHORITY\NETWORK SERVICE, the account used for the SharePoint timer service and the central administration site, is highly privileged and should not be used for any other services on any machines in the server farm. The following services were found to use this account: SharePoint - 80 (Application Pool)
SPUserCodeV4(Windows Service)
OSearch14(Windows Service)
Web Analytics Data Processing Service(Windows Service)
All required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm.
Upgrade is required on server MATS-PC. Without the upgrade, the server is not in a supported state.
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
SharePoint_Config_c5681991-3bec-45b3-9376-ea8c19c51b6a,
SharePoint_AdminContent_39d0c8e9-214e-42b9-909e-ffbe4147208b,
WSS_Content,
WSS_Search_MATS-PC,
WSS_Logging.
Those seemed to be the most relevant. Hm. I have no clue? Especially about the upgrading? I didn't upgrade anything recently.
Especially about the upgrading? I didn't upgrade anything recently.
This sounds a lot like a Microsoft Update. Service packs for SQL Server come through Microsoft Update, and if you applied those without checking carefully, some of them produce similar symptoms to what you're describing. SQL Server can take longer to start up, and when that happens, sometimes antivirus software grabs the MDF/LDF files for scanning. That will cause the databases to be unavailable, and other services will then fail on startup.
When you started SQL manually, things started working again, but now you've got version dependency problems. You're lucky SQL even starts, though - I've had clients with issues where SQL won't start after careless SP applications if they had changed the SA login, for example.
The errors you got while doing the reboot where just because the SQL Service did not startup. No database = no SharePoint. This happens to me all the time.
The other messages in Central Administration are nothing to do with your SQL startup and chances are they have been there for some time.
As any other developer on a single box hosting SharePoint, you have permissioned stuff with a single powerful account. Central Admin now detects this and gives you the warning.
It looks like the SharePoint versions of one or more of your server databases are out of sync with the version of 2010? Not exactly sure how it got into this state, but for a dev box I would not be completely stressed. An upgrade to the new service pack hopefully would sort this out.