I have been playing around the Azure virtual machines and have setup successfully a Web Application VM and an Azure Database/ReportServer 2014 VM .
My current build works fine on all browser and am able to generate reports locally if I am to connect to my local ReportServer(MSRS12).
However, If I point it to the Azure ReportServer(MSRS12), I am unable to generate specific reports and only returns a blank report data.
Currently I have two set of reports. First is the report with a static parameters namely just the year. This report is generated normally.
Second reports are the one that is dynamically mapped parameters. Theses reports only returns blank report data with parameter control still active.
Upon checking the Report Server Execution Logs on the database, I found out that The first report were executed just fine.
The second reports are executing normally but returns a blank report data with very short loading times. Normally the reports take about 1-3 minutes to render.
Checking again the Report Server Execution Logs on the database, second report were not executed at all. Not even a record of a failure of execution.
My current setup in Azure Database/ReportServer are just the default and have not changed anything regarding the security aside from the inbound rules to allow access to SQL traffics.
Site is currently done in asp.net, and code is in C#.
So far I have done the following:
Updated ReportViewer dlls.
set AsyncRendering = false
set element.style.overflow = "visible"
Related
I have never used reports before and my knowledge is really limited. I have developed an application using C# and SQL Server 2012 Express and one of the features is to show customers account in ReportViewer.
This report gets its data from a stored procedure and for now everything works fine, but the client wants it to work on the desktop of several different machines.
So I made one machine work as a server with the others connecting to it by router and everything in the application works fine except the ReportViewer shows only a blank white report (but only on the client machines -- not the server)
I also tried updating the dataset's connection string in app.config.
What should I try next?
I am an intern, our companies report guru was my mentor, but he left 8 months ago and I have inherited his report responsibility.
We are deploying some new servers. I have set up new reports and connections for the INT and STG versions. I have full access to these two servers.
I do not have any permissions for PROD. Our DBA has created the Shared Data Source on the target server. (He created all of the Shared Data Sources on the servers first)
I have attempted to create and connect the Shared Data Source in Report Designer to the Shared Data Source on the PROD server. I have failed.
I have managed reports on our system that point to servers I have no access to. Their shared data sources where set up before my time with the company.
1st Question. Can you successfully set up a Shared Data Source in Report Designer if you have no permissions on the target server?
http://technet.microsoft.com/en-us/library/ms155845.aspx
I have perused this page, and will quote what I feel is most pertinent.
"To create a shared data source or modify its properties, you must have Manage data sources permissions on the report server. If the report server runs in native mode, you can use Report Manager to create and configure the shared data source. If the report server runs in SharePoint integrated mode, you can use the application pages on a SharePoint site. For any report server regardless of its mode, you can create a shared data source in Report Designer and then publish it to a target server. "
2nd Question. Does order of operations matter in this case? The last sentence says I can create the data source and then publish it to the server. Would that provide different results then creating it on the server first, and then creating it in Report Designer?(In INT and STG our reports deployed properly with this second method)
Thank you for taking the time to answer these two questions. I hope my background information was clear enough.
Question 1. Yes, you can.
Question 2. Unsure.
My personal problem ended up being a firewall issue. Once the firewall issue was taken care of I was able to successfully set up the connection and deploy the working report on the server.
There have been some minor issues with the set up of the connection. This leads me to believe that the ideal order to set up the connections would be to create the shared data source in Report Designer and publish it to the target server.
I have not been able to replicate the precise problem, so the issue might just be between the keyboard and the chair and there is actually no issue changing the order of operations.
I have got a silverlight application, it works fine locally and all the data with displayed on the application but when I publish the same version to Live, most of the fields on the application will not display the data.
I have checked everything, stored procs, connection string and all other possible stuff but some of the fields won't display the data at all. The application uses the stored proc, when I run the same on the server returns data properly.
I have tried all possibilities, but couldn't find any solution, does anyone have any idea about this.
Thanks
I have problems connecting to the report's database. In my log I see that an exception is thrown : "Log on failed".
This is what I do: I am using a service that needs to massive generate reports. When opening the report with Crystal Reports everything is ok, but when using this service, it throws an exception saying log on failed.
I tried Verify Database from the menu in Crystal Reports but it says everything is up to date. My service uses a batch for massive generating reports on the server. I am unable to connect to the database.
I think that there are some security issues when trying to connect to the database like this. I can't do any debug, except logging my steps.
Please help !
Have you tried a "canned" Crystal Reports batch scheduler like:
http://www.reportrunner.com
http://www.christainsteven.com
I am having a problem with data not updating on the CRM at my wife's office.
Scenario:
User loads the app.
Data from the DB populates the master view.
User opens edit screen.
Data is populated for the correct detail item.
User changes a value (on any field).
The save button becomes active with
the data change.
The user clicks on save.
The data is refreshed on the edit screen (to prove the update took) and the original data is restored to the edit screen.
The save button is disabled.
Looking at the master data grid,
behind the edit screen, the data
appears to be updated.
Close the edit screen, the new data
is still visible in the master view.
Click on refresh and the master data
reverts to the original content.
All changes are lost.
If I run the exact same scenario on my dev network, the database IS updated.
So what is different between the two environments? There is a domain at the office. I'm using SQL Authentication so it shouldn't matter. I'm running a Win2003 EE with MS SQL 2005 EE VM for my test DB server, which mimics the office DB server. I use backups of the production DB to populate my dev DB. I have double-checked the SQL user permissions. There are no errors in the Event Viewer or in the SQL logs on the DB server. All workstations are Win7 Ent. I run x64 at home, while the office machines are x86. Walking through the code on my machine doesn't provide any insight because everything works in my dev environment.
The app has been around since December 2008. I do monthly updates at a minimum.
ClickOnce deployment.
I need to run SQL Profiler to gatehr more info. Beyond that, I'm clueless. What is really happening? Why does it work in dev and not in prod? Any suggestions on how to track this down?
Thx,
Ivan
after starting the application, but just before save is clicked, rename the table in sql server management studio. See if the application throws an error about the table not existing. If you don't get an error, then C# isn't trying to update the database. if you get the error rename the table back, add a trigger on the table to write to a log table, restart the application, and try the save. check in the log table, did it insert anything? go from there.