My extension has a few hundred downloads daily.
For every user that installs I create a user in my database.
I report back to the server that the user is still active every time the extension starts and every 2-3 (random range) hours after that.
I've set the uninstall url so when a user uninstalls the extension a page opens and I mark the user as uninstalled.
I see roughly 10% uninstall rate within two days of the install.
The problem is that 50% of the users disappear, meaning they do not report activity for a week or more.
I've managed to rule out:
Users disabling the extension.
Users syncing the extension across machines, then removing on one machine which removes it from the rest of the machines.
What else can it be???
Did anyone else experience that?
Related
A couple of weeks ago, our Access application suddenly began to fail mysteriously. Comboboxes on random forms would not fill with rows when recordsources were set. These include forms that have not changed in years. Stepping through the code in the debugger always results in a successful outcome. Trying multiple times consecutively would occasionally work. One or two computers still work reliably, though these have a source control addon called Ivercy installed. When you run the deployed version (without the addon active) these machines show the same unreliability.
Last week, we found more issues including some forms and reports that would not populate on initial opening. Reselecting the same filter date (or other rowsource changes) once the form is open brings up the expected set of rows. Again, loading the form while stepping through the code always works.
These behaviours lead me to believe there is some sort of fault that has been introduced in a recent Access update. Has anyone else seen this kind of problem?
One instance of this issue occurs on a very simple, one page report that has no user code in it at all. I would have been willing to believe that we had been doing something systematically wrong in our code, but this code-less report seems to suggest otherwise.
My machine (which exhibits the problem) is using Microsoft 365 Apps for enterprise
Version 2105 (Build 14026.20308 Click-to-Run)
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 built and successfully split an Access 2013 db. The front end worked fine for months up until I last used it a few months ago. I recently went to open the front end but the Access window was frozen whereby everything (e.g., navigation pane, menus, controls, right click, etc.) was disabled, including the window control buttons to minimize, expand and close. The only way to close the view was to right click the Access icon in the task bar or 'ctrl-alt-delete' to open task manager and force close the application. I was met w/ similar results when attempting to open other versions of the linked front end; however, I can successfully open the back end and other Access db files that don't contain linked tables. When I get the 'frozen' screen I can see my linked tables and other db objects in the navigation pane, but the pop-up login form does not display and the entire window behaves like it is inactive, similar to how it behaves when selecting items behind the active login form.
To confuse matters even worse, I have one user (User 1) who has the same user permissions as me who does not experience any of the problems I described above and can work within the front end as expected; in fact, he and I are the only active users as we are still in the developmental phase of our project. One other layer of complexity, he tried to open the file w/ his network profile from my computer and ran into the same problems. We have one other user who we've since tested this problem with and she experiences the same issues as me on both her laptop and PC.
So, I thought maybe it had to do with the 32-bit version I unknowingly had installed when my OS was re-installed last month since User 1 had the 64-bit version which could explain why he couldn't open from my computer. BUT, I still experienced the same issues after re-installing the 64-bit version on my computer. I'm at a loss on where/how to proceed from here and my IT guys have done all they can to troubleshoot my problem as they are not familiar w/ Access and aren't much help at this point.
Anyone run into this problem before? Thoughts or possible solutions? Any and all help would be greatly appreciated, thank you.
So, I disabled the code that prompted the login form and I was able to open the file. Based on User 1's experience, we determined that he hadn't installed updates since I was last able to open the file. As a result, we determined that an update I installed was not compatible w/ the aforementioned code resulting in the problems I described in my original post. I will re-create the code that drives the form's login and keep an uncoded version as back-up in case we experience similar issues in future updates so that we can troubleshoot from within the db rather than be locked out as we were.
Hope it's the right place to ask this question - usually I use SO to ask about programming...
I'm doing a project that involves Crystal Reports Server. From code, I'm able to schedule reports successfully, but when I look at the BI launch pad I don't see the report in My Recently Run Documents (I see failed reports in that list - ones that has wrong database credentials).
When I go to Central Management Console and I find my reports in folders and I go to Properties > History I see the report status as "Running" - and it has been like that for a long while (too long than it should) for 2 different reports I have sent.
How can I diagnose what the problem is? and why it is stuck? there are no error messages anywhere about it.
How can I get a full history of all reports in the system (not just one single report at a time)? and how can I see currently running reports?
How can I stop a running report?
I really hope this is the right place for these kind of questions... if not, would be very happy to get a referral.
Thanks
How can I get a full history of all reports in the system?
Open the CMC and then click on the Instance Manager. At the bottom of the page, you can filter on the object type and status. That way, you can get a full overview of all running reports on your platform.
How can I stop a running report?
If you select a running instance (either in a document's history page or in the Instance Manager), you'll notice that there is no stop button. Instead, you have to delete the running instance. It might not stop running immediately though (depending on what it's doing), but it will be removed immediately from the list of instances.
How can I diagnose what the problem is?
What I would recommend is to enable tracing on all related servers (thus your job server, processing server, etc) and then retry scheduling the report. This should generate additional logging on the server which you can use to diagnose the issue.
The trace files have the extension .glf (generic log file) and are located in the logging folder on your Crystal Server. Have a look at the command-line property of each of the servers for which you're enabling the tracing, you should find a log folder there somewhere.
Make sure to turn the tracing off again as soon as you're finished, as tracing will not only create extra strain on your servers (causing the system to slow down), but it will also result in very large log files.
Before starting with tracing, have a look at the existing log files to see if it doesn't already contain error messages that might help you diagnose the issue. Sort the log files by date, and look at the most recent one for each of the servers involved. If there's nothing in there, start with tracing, but remove the existing .glf files to minimise log contamination (some files will be locked, just ignore them).
I've got an Access VBA application that is responsible for querying a SQL table once per second over ODBC, looking for records where processed = 0. When it finds one, it will process an Access report and print it to PDF using CutePDF, saving it to a network drive that our desktop application (that added the SQL record with processed = 0) can access, opening it on the user's desktop.
I've spent considerable time debugging this, my first VBA application, and have all errors being trapped & logged. This morning, the Access application was closed, so no reports were being processed. Opening the .accdb allowed the backlog of reports to begin processing. The error log is empty, and the server has not rebooted in nearly a month.
As far as I know, this application should ONLY be run from a desktop, so an administrator must log into the server after a reboot. I've read that running MSACCESS as a service is a "terrible idea" and exposes Windows to corruption if Access errors out.
That's the state of things. Here are my questions.
Is there a pre-written application you would recommend that I install
on this server to monitor & log the events of the application
(particularly, exits & opens)?
As a last resort, I suppose I could
add a function that, every 10 minutes, writes to a "status log" text
file that basically says, "I am here!" so that I can at least find
out WHEN an app closed, if not WHY. This seems like overkill, as the log file could grow enormous unless I create & destroy it every 5-10 minutes instead of appending it.
You'll have to forgive me, prior to this app I worked exclusively on PHP & JavaScript, and haven't taken a Visual Basic or C-based class since college 6 years ago.
Any creative solutions?
My 1st thought is use the Profiler to capture what you need.
Does your app reset the processed = 0 flags when the reports are created?
You could have a 1 record table with a 'last processed' date field, and just update that everytime it runs.