I have a reports application which uses Crystal Reports XI R2 as its engine which is deployed on an Windows 2008 Server. The problem is, on some data heavy reports it fails to show the report. Some reports work but others... don't.
My end shows a firewall error, when I do a remote desktop and run the same report I see a timeout error. Funny thing is the same report shows correctly when it is deployed on my localhost(No, I do not mean running it via Visual Studio, I set up the IIS deployed the app in the same manner I did on the server) or when I connect to server via Remote Desktop Connection and run it from there.
Any ideas on where should I look? What should I check? Windows error logs do not show anything amiss.
Thanks..
Related
I am sure that someone was successful to deployed SSRS report on the server where
SSRS is configured to access Oracle database.
I developed report on my machine where I have Visual Studio 2017,
ODTwithODAC122011 64-bit; 32-bit ODT withODAC122011. I connect to Oracle database and can run report.
After i deployed this report on Windows Server 2016. i got an error "An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'ORACLE' that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound".
I tried to complete the same ODAC install as on my machine.
1)Installed ODTwithODAC122011 64-bit - configured TNS name.
but with step
2) i tried to install 32-bit ODT - I received error that i need to install Visual studio to proceed with installation.
Do i really need VS on the server? What is the possible solution you can share?
thank you --Angelika--
with only the Oracla.DataAccess library should be enough, on the root of the service. Be aware the versions be the same as indicated in the project references
I am trying to debug a webservice remote on Microsoft Azure. The service is running in a web role.
I have configured remote debugging in the publish settings an can attach the debugger to the web role. Also, when I have selected the correct process, the debug symbols are loaded correctly and breakpoint's tool tips say that the breakpoint is hosted in "WallSHost.exe" which is the remote process.
What I would like to do, is to run a local client software which I am developing and step into the server code from there. When I step into the according service client call (F11), I get the above error message, saying (for the sake of Google in plain text here):
Unable to automatically step into server. Connecting to the server
machine 'xyz.cloudapp.net' failed. The Microsoft Visual Studio Remote
Debugging Monitor (MSVSMON.EXE) does not appear to be running on the
remote computer. This may be because a firewall is preventing
communication to the remote computer.
I have tried to disable the firewall on my (the client) machine with no effect. Has anybody seen that before or can tell me how fix this problem?
A quick checklist
deployed cloud service is a debug build
a debug build is selected from Build Configuration list (in publish wizard)
'Enable Remote Debugger For All Roles' is checked
no changes to code since deployment
I'm working with Selenium in VB.NET using IEDriver. I want to launch my ordered tests suite on my windows server 2008 R2 (My server used IE 11). I launch my test by command line : vstest.console.exe.
When I launch this on Windows 7, that works. I try to launch it on my server ( OS : windows server 2008 R2). That launch my Internet Explorer and my first page test. My test fail on the first try to find element (text input) and send key . However the element is present on my web page and I launch on the same website. I don't know where is my problem. I have some idea :
IE Driver compatibility with Windows Server 2008 R2 can't modify
Security server, some rights don't allow my driver to interact with IE
Problem in my code tests (Impossible for me, because the same code run perfectly on the same website)
Someone have any idea ?
This seems like a problem with windows server. Look for installed updates in server. This will probably occur because of that. Windows sometimes install updates without telling you and there are some updates that tamper with IEdriver and breakes it
All the sudden started getting the following error while trying to debug a worker role:
"Windows Azure Tools for Microsoft Visual Studio
There was an error attaching the debugger to the role instance 'deployment16(360)blah blah' with Process Id: '8780'. Unable to attach. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
Restarting Visual Studio and the machine do not help.
As you start getting this problem all of sudden in your development machine something must have changed and it is mostly due to some of the OS auto-update and/or some application update you installed in your machine. There could be any random reason for this problem however if I would have hit the exact same problem here is what I would do to troubleshoot such issue:
To start, first thing is to just check it is not an application specific problem by creating a base app from web/worker template and see if that exhibit the problem.
If you have installed new release Windows Azure SDK 1.7 check with both SDK 1.6 and 1.7 to verify if both exhibit the problem.
Check if your could debug IIS based application as well outside Compute Emulator. This will isolate if the problem is specific to Windows Azure development Fabric or bind to your IIS itself.
If this is IIS specific issue, Check IIS configuration for all enabled functionalities, try resetting Application Pool configuration, running "ASPnet_regiis -i" etc to fix the issue.
If it is Windows Azure Computer Emulator specific, I know sometime OS updates may make application unstable so in that case, I will re-install .net 4.0 and VS2010 SP1 again respectively. (This does help so many time) then re-install Azure SDK 1.7 completely.
Such random problem mostly occur due to some change in your machine configuration, so restoring the VS2010 and the re-installing all other application does help to solve problems.
If you have an exception in the role's OnStart() or in Application_Start() that the debugger doesn't pick up, you may also receive this message. Application_Start() errors are especially pernicious because the debugger doesn't attach to the web process until after this method returns.
If you are wedded to cloud specific classes such as RoleEnvironment and cannot make the web role a startup project, you can use Ctrl-F5 to run the cloud project without debugging. With some luck you'll get a yellow screen of death to show you the true error.
Avkash covers the points.
I had the same issue recently. I set my web project as start-up rather than Azure and I discovered that that web project didn't actually run. Turned out somehow when of my projects was compiling for X64. I changed that and it worked.
We've got an old VB6 app which uses Crystal Reports XI Release 2 to run reports against a SQL Server 2005 database. This has worked well over the years. Also, for the last upteen years we've used Windows XP. Well, we're beginning to migrate to Windows 7. Well, now one of the users on Windows 7 cannot run the report. It gives him an error of “Logon failed. Details: [Database Vendor Code: 6]”. All of the Crystal Reports used in this application use an system ODBC connection. I've verified, twice, that the system DNS properly authenticates against the SQL Server database. However, when the user attempts to run any of the reports in the VB6 app, they all give that same error. The weird thing is we've got another old VB6 app, which also uses Crystal Reports, and that app's reports work fine. But that app runs against a local Microsoft Access database, not against SQL Server.
So the question is, are there any known issues involving SQL Server, Crystal Reports XI Release 2 and Windows 7?
Something else we just noticed. On the 2 user machines that are exhibiting this problem, both are 64-bit Windows 7 machines. So, could it instead be an issue of a 64-bit version of Windows, SQL Server and Crystal Reports XI Release 2?
Crystal Report 11.5 does run on 64 bit windows. Minimum req.ment is CR11 R2 SP6 to run on 64 bit.