QBFC11 and QBFC12, VB.Net 2008, QB ES 13
We have seen this a couple of times in different applications at different clients.
When our program adds a customer it can take up to 8 minutes each.
One customer seen this fell back to a prior QB version and the problem immediately dissappeared.
Is there a QB patch that fixes this?
Recommendations???
Related
For the last 3-4 weeks now, when I login to our SSRS from home, I have to re-enter my credentials no less than 15 times (this is NOT an exaggeration) before I can use the site. Internally, it never asked for credentials until this time.
On the server, I'm running Server 2016 with all of the latest patches and SQL/SSRS 2016 (13.0.5820.21). On my home workstation, I'm running Windows 10 Home Edition. On my desktop at work, I'm running Windows 10 Pro attached to the domain. I remote into my workstation for development work and do everything else locally on my PC at home.
I'm wondering if there was a recent Windows 10 update that may have mangled this up? I'm not hearing complaints from my users and I know general user workstations are significantly delayed for receiving Windows updates.
Any assistance with this horrible bug is appreciated.
After upgrade to TFS 2018 Update 2 (with Azure DevOps 2019 still persisting), some service hooks messages are not sent correctly but are stuck in the queue with status Queued or Processing (see the image). Messages in Processing state appear to be delivered correctly to the receiver, the ones in Queued state not. Service hooks are working for 1-2 days correctly after a restart, next days are more and more buggy. Receiver side is ok, many times tested.
This happens on all service hooks (some are HTTP webhooks, other posts to Teams), in 2 of our 3 collections. On the 3rd collection, it works without issues. Disable/Enable or recreating the hook doesn't help. Is there any way how to debug service hooks or some log.
Also reported here. Received several patches from MS but with the same result. Installed Azure DevOps 2019 with the same results.
Any help would be appreciated.
The answer is - this is a Microsoft and TFS problem. After several months of communication with Microsoft and trying several patches for this problem, finally, the right patch arrived. And the problem is solved.
The patch is non-public now, so if you are experiencing a similar problem, ask Microsoft support.
Edit: Problem is fixed also in official release 2019.0.1. See Release notes
I am working on an application that will automatically insert into my clients QuickBooks Online Edition database. I have the xml format but now I need to do some testing to make sure the inserts go into the QBOE database correctly. Is there a QuickBooks Online Edition test environment?
Getting onto the Intuit test environment requires submitting an application for review to become a premium IDN developer (much too hard considering I only need a couple of days for testing and more expensive than the solution below).
To be able to test a small application for QBOE, I just created a new QuickBooks Online Edition account/company - signed up for the 30 day free trial. 30 days is more than enough for me to complete my testing... and even if I need more time the basic version is $9.95/month which is completely acceptable in my mind if I want to keep the account around for future testing or contract work.
See this IDN thread for a little more details.
I have been running an intranet using SharePoint 2007 for over a year and all has been working fine. However, after some time, I realized that the intranet portal was slow. Trying to access the Central Admin over another computer not the SharePoint server also became an issue. So I logged onto the real SharePoint Server and it took some ages to login and then was so slow even on the server unlike other times.
When I checked the Task Manager, I found out that w3wp.exe was consuming 99% of the CPU speed. When I restarted the Central Admin App Pool, everything came back to normal and all was running well but after a few minutes (15 or so), it again became slow.
I have checked the Event Logs and nothing conclusive was there to help me out. Anyone who has had this experience? or has any good resource? Please help. Thanks in advance
Are you having any problems with OWSTIMER.EXE by any chance? Have you considered using Process Explorer to monitor CPU usage? Specifically, this would help you determine which Web Application was slowing you down provided that it is a single Web App. What do your logs say in the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS folder?
I've had similar problems. Let me know more about your problem and I'll show you what I've found.
For those who might be interested and facing the same problem. I was using SharePoint 2007 RTM and when I upgraded it to SharePoint 2007 SP2. The problem was resolved. I am not sure what was causing it but SP2 has many performance improvements and possibly it had the fix.
We have a few backend windows services written in .net framework 1.1 running and on December 31st 2008 around 5.00 pm (EST) we stopped these services to run some year end reports.After the reports were run , we tried to start the services and the moment we attempt , it would give an error "Service did not start in a timely fashion".We tried every possible things that google came up with.Service Packs , WinDbg , GFlags etc etc.
Finally we called in Microsoft support around 10.30pm(we had premium support contract with Microsoft) and they started collecting all kinds of server data and around 12.05 am (EST) the services starting successfully with no issues.We hadn't done anything different or special to get it started.The whole team was stumped as to what was happening and equally glad that it was working.
The conclusion is Microsoft support team thinks that this could very well be something to do with the .NET Framework 1.1 namepsace System.ServiceProcess.ServiceBase inability to support leap year.They havent confirmed it yet and are still investigating.
I will keep posted as and when I have updates form MSFT support.I was planning for a dreadful 2009 start but gladly it all ended fine.
I wonder if the bug is related to the one that causes Zune 30GBs to lock up on 31 December in leap years: it tests for day>365 in one place and day>366 in another and as a result when day=366 it falls through the second test and goes in to an infinite loop.