I am following the tutorials for reporting services on the microsoft website and currently on: this tutorial.
I am just going to the web portal on my local host, going to the data source option of the report, but it is impossible to change something when I select "Use the following credentials"( see below screen). what you don't see on the screen for some reason is that the cursor becomew a probibited sign when hovering over the field "user name" or "password".
I tried it in several browers (edge, IE, firefox and Chrome), but everywhere it is the same. I am logged on as administrator, so I would assume it is not a permission issue (altough the change in cursor makes me suspect otherwise).
I tried googling the subject for an hour or 2, but i didn't come across any useful information. As far as I can tell I configured the Reporting service correctly.
I do notice that the first time I open the "Manage" menu of a report I only see the options "properties" and "security". When Inavigate back to the menu and try again I suddenly see all menu options like you see on the screenshot. I also often get the pop up "something went wrong, please try again later"
I am running windows 10 on my laptop and installed SQL server express 2017. I did read that SQL express does not support all features of the reporting services, could that be the root cause of the issue's?
I know this is quite vague, that is also what makes it hard for me to look it up... I hope someone else out there has encountered the same :)
Thanks for the input!
To answer my own question:
I was stupid enough to use SQL Express edition and this does not have all the features required to run SQL reporting services. After installing SQL developer edition all worked as it should.
Related
When running SSRS Reports that have many parameters that users will change and click view report to see different results, chrome security will intermittently prompt for Sign In. When it does, valid credentials will not work.
This started happening with the latest chrome update where the tabs because curved about two months ago.
IE and Edge work fine (albeit much slower)
The Datasource uses a sql login with full access to the SQL Server.
The end users are on windows auth and should not be prompted once authenticated.
Same report has worked for a long time prior to latest update and works in other browsers. Chrome Canary does the same thing. All Chrome users are having this same issue rendering chrome unusable for SSRS.
I have access to the reporting services log file, but there is lots of traffic so very hard to read.
I can run profiler, but the server is very busy and I'm since I'm not sure what to look for, leaving it wide open has so many other threads from other users and it seems even my spid changes constantly as ssrs moves through the requests. Enter report, view report, view report, view report, etc..
Cannot find anything close on google except old stuff that we've went through with chrome using the ie lan advanced security settings. None of the old stuff helps. Have also check ssrs configs to make sure we are forcing windows auth and it is.
Any help with the actual problem or even help with how to troubleshoot this would be greatly appreciated.
Screenshot provided just after hitting view report for the third time. Correct credentials will not work at this point.
Ken . . .
Resolved as a Digital Guardian network tool blocking.
I have a report in Microsoft Access 97 (yes, I know) that works properly on my client's copy of Server 2003. However, when I try to run it on my own copy of Server 2003, the report crashes Access immediately. It does the same in Server 2008 R2 and Server 2012 R2. Now, the interesting thing is that the query underneath that report runs perfectly, which I would think rules out things like MDAC. There's nothing unusual about the report -- no strange fonts or graphics -- at least nothing obvious. If I can get it working in an environment identical to the client's, then I can move it forward to other operating systems. Where should I start looking for the cause?
Usually this kind of crash is related to missing references..You need to go to the VBA Editor (ALT + F11) -> Tools -> References and check if you have any MISSING
Import everything from your current project into a new blank project, seems like that is the only resolution I have been able to find online.
The information that I found can be viewed here: http://www.pcreview.co.uk/threads/access-97-crashes-opening-a-report.3901588/
What worked for me, don't ask me why:
I found the printing worked and so did Layout View
Open the report in Layout View
Save the report
It works!
I'm having a very peculiar issue with SQL Server Data Tools 2012. Whenever I attempt to launch the report previewer, I get the following exception:
There was no endpoint listening at net.pipe://localhost/PreviewProcessingServce7324/ReportProcessing that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more deatils.
As far as I can tell, nothing I did triggered the issue. It just started happening one day when I fired up SSDT. I tried the suggestion on
Report Designer Preview in SSDT throws up a 'end point' not found error.
However, my service is up and running just fine (restarting it didn't help), and using Setspn didn't do anything for it, either.
Anyone have any ideas?
That is a current bug in SSDT-BI. The current workaround for now is to right click on the report you want to preview in your Solution Explorer and click RUN.
You will also notice that if you try to preview the report for the first time a command prompt window opens up that runs the preview process, If you don't close this window and just minimize it then you can preview the report but I think the RUN method is much easier for now. Please mark as answer if this helped.
This can happen when you have some SQL Services installed and running on your machine that interfere with the Report Preview. You can check your current services by going opening Sql Server Configuration Manager:
To fix this you can do the following:
Type WinKey + R, input services.msc in the Run box, and press Enter.
Find the "Net.Pipe Listener Adapter" and either Restart or Disable it.
The workaround, as SQLnbe mentioned, is to:
Right Click the RDLC file from solution explorer
Click "Run" from there which will open up a new window.
The Preview issue was resolved for me when I deleted the .DATA files associated with the solution.
In my case I tried all the above solutions, and:
"Run" from context menu does not really work for me, as it's much, much longer than preview in VS2017, as rendering was a deciding factor in my work (lots of grouping by column etc). and render is much faster in VS compared to SSRS,
Could not find listed .Net services on my laptop,
Deleting DATA files did not fixed the issue either,
VS restart and reloading the solution.
I'm not sure if it was points 3 and 4 together that actually did the trick, but I'm putting it out there - just in case it actually is the procedure that will work for others, which is to try option 4.
I need to also note that this issue started after there was a momentary connection dropout. I need to work with WIFI instead LAN due to necessity to be roam-able, and every time I undock the laptop all my connections in SSMS are lost (and with them all the temp tables etc).
I faced the same issue and solved it.
Steps:
Right click on the report.
Click view code.
Check the parameters names in both query parameters and report parameters and make sure it's written correctly.
Close the report and open it again
Thanks
This is what I did:
Restart the .Net.Pipe service in the service console. This didn't resolve the issues.
Closed Visual Studio completely and relaunch the Visual Studio 2017 (in my case).
It seem that the preview is back. It could be the combination of (1) and (2).
None of the solution above worked for me. What did I found and it worked is to run Visual Studio as administrator.
Just closing the visual Studio by ending task with task manager and re-opening the solution worked for me to get through the error.
OK so this is kind of a general question here. We run an ASP/C# Site that's fed by a SQL 2008 R2 database.
Our data entry takes place using Microsoft Access 2007 and feeds to a SQL 2008 R2 instance.
Our data entry forms (all .adp) are generally simple, but we randomly run into problems where I'll post a change to the DB (we have a script that runs at night and will archive our old DB versions in the form of "DB_NAME.adp03122012" and keeps the newest revision as "DB_NAME.adp". This way, our data entry team will just need to click on a network shortcut to access the Access forms.
What we're running into is non-reproducible errors of varying types on random machines.
Example, I make a simple search that has a combo box and a search button. You select the item you want to search for and it updates the record source to search for that PK/FK. It works fine on my developer box. It works fine on certain end-user boxes. But on others, it throws a run-time error:
"Run-time error 2467: The expression you entered refers to an object
that is closed or doesn't exist".
Now the error itself isn't the focus of this. It's not being able to reproduce it. I tried running it on another box that has the same hardware specs as the offending box and it ran fine, no errors, no nothing.
I'm at an absolute loss as to why this is happening. I don't think the error is actually related to my VB code or to our databases, as it's working fine on some computers and isn't working on others. It's almost as if the code isn't propagating properly to specific boxes.
Has anybody else dealt with this before?
I feel somewhat foolish, but our Network Admin hadn't propagated Windows updates to all of our end user boxes.
The advice that Remou and mwolfe02 gave was valid and helpful, and likely would've helped had I been informed that the computers in question needed updates.
Thank you for reading and offering comments and help.
I'm trying to get rid of the /reports directory which seems to be integrated with SQL reporting services 2008. I'm unable to uninstall that one element of SQL server and I've had no luck when trying to reconfigure the ReportBuilderLaunchURL. Does anyone out there know how I can get rid of this stupid feature? I'd understand if it was just a virtual directory on the localhost instance but when it gets applied to all my site I get really frustrated and wonder who at Microsoft decided that this would be the default setting.
For future reference:
Use the "reporting services configuration manager".
In the report manager URL tab insert a new virtual directory.
I believe you uninstall SSRS by going through the installation process of SQL Server itself and selecting to remove a certain component (SSRS in this case).
Alternatively (probably better) is to go to the Add/Remove programs menu and select SQL Server and hit the "change" button. From there you will be given the option of the components you want to repair/install/uninstall/etc.
Edit: Here is an article I found which attempts to describe how to uninstall SSRS 2008. It seems to agree with what I was saying about the Add/Remove programs idea.
We've just been having this issue and the work around we came up with was linking it to one specific host header, rather than having it point to all sites on all IP addresses. (You can do this by clicking on the advanced button in the URL tab that #Luis mentions.) This has, effectively, quarantined the thing to one website and as it's a host header that isn't on any public site in the first place, it's massively limited the number of people who can even find it.