We have a client that has installed our app in a Citrix environment on their server. Sometimes QuickBooks will connect and other times it gets the following error in qbsdklog.txt
20171212.145407 I 15312 RequestProcessor ========= Started Connection =========
20171212.145407 I 15312 RequestProcessor Request Processor, QBXMLRP2 v13.0
20171212.145407 I 15312 RequestProcessor Connection opened by app named 'Well Profits - SherWare, Inc.'
20171212.145407 I 15312 RequestProcessor OS: Microsoft Windows Server 2008 R2 Datacenter Edition Service Pack 1 (build 7601), 64-bit
20171212.145407 I 15312 RequestProcessor Current User is in AdminGroup
20171212.145407 I 15312 RequestProcessor Current Process Integrity Level : 2000
20171212.145407 I 15312 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20171212.145407 I 15312 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20171212.145408 I 15312 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20171212.145408 I 15312 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20171212.145409 I 15312 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20171212.145409 E 15312 RequestProcessor Could not find or create an instance of QuickBooks using InstanceFinder
QuickBooks is already running and has the QuickBooks company open.
Anybody have success running consistently under Citrix?
Related
I have created a .net core 3.1 console application for reading azure service bus queue messages and deployed the EXE in a client on-premise VM. It was working initially but now it is not working from VM (now also working from local machine). I am getting a time-out (socket exception) while executing the exe in on-premise VM. I am using shared access policy connection strung to connect the service bus.
Exception :
Azure.Messaging.ServiceBus.ServiceBusException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ErrorCode: TimedOut (ServiceCommunicationProblem)
---> System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
at Microsoft.Azure.Amqp.Transport.TransportStream.EndRead(IAsyncResult asyncResult)
at Microsoft.Azure.Amqp.Transport.TransportStream.<>c__DisplayClass22_0.b__1(IAsyncResult a)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
The most common connection issue in an enterprise environment is that the ports needed for AMQP over TCP (5671/5672) are not open. Changing the transport to AMQP over WebSockets often helps, as it will use port 443 and may be routed through a proxy, if needed.
Both the transport and the proxy (if needed) can be specified using the ServiceBusClientOptions when creating your client:
var options = new ServiceBusClientOptions
(
TransportType = ServiceBusTransportType.AmqpWebSockets,
WebProxy = new WebProxy("https://proxyserver:80", true)
};
var client = new ServiceBusClient("<< CONNECTION STRING >>", options);
For more information, you may want to look at the Service Bus troubleshooting guide.
I am running an ASP.NET MVC application on IIS 8.5.9600.16384 under Windows Server 2012 R2 Standard. Sometimes I get below error in the event log that makes my application not responding for a while.
Event ID 5010 - Source: WAS
A process serving application pool 'AppPool name' failed to respond to
a ping. The process id was '.
My website uses Web Garden and its application pool is set to 4 worker processes and using mode StateServer. Also application pool identity is set to a domain account.
ASP.NET State service runs in the same machine where my site is published.
Any ideas about what could be the problem?
apparently with no specific reason, and with nothing on neo4j logs, our application is getting this:
2019-01-30 14:15:08,715 WARN com.calenco.core.content3.ContentHandler:177 - Unable to acquire connection from the pool within configured maximum time of 60000ms
org.neo4j.driver.v1.exceptions.ClientException: Unable to acquire connection from the pool within configured maximum time of 60000ms
at org.neo4j.driver.internal.async.pool.ConnectionPoolImpl.processAcquisitionError(ConnectionPoolImpl.java:192)
at org.neo4j.driver.internal.async.pool.ConnectionPoolImpl.lambda$acquire$0(ConnectionPoolImpl.java:89)
at java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:822)
at java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:797)
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
at org.neo4j.driver.internal.util.Futures.lambda$asCompletionStage$0(Futures.java:78)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:507)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:481)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.access$000(DefaultPromise.java:34)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise$1.run(DefaultPromise.java:431)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at org.neo4j.driver.internal.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
at java.lang.Thread.run(Thread.java:745)
The neo4j server is still running, and answering requests to either its web browser console, or the cypher-shell CLI. Also, restarting our application re-acquires the connection to neo4j with no issue.
Our application is connecting to neo4j once when it's started and then keeps that connection open for as lunch as it's running, opening and closing sessions against that connection as needed to fulfill the received requests.
It's the 2nd time in less than a month that we see the above exception thrown.
Any ideas?
Thanks in advance
I have a Quickbooks "Integrated Application" written in C# using QBFC 12.0. It is installed and working correctly at a number of sites with several versions of Quickbooks. Today I tried to install it at a new site with Quickbooks 2012 Premiere. To authorize the application to connect it is necessary to open QB, logging in as the QB administrator, then initiate a connection from the integrated application. This has to be done each time I install the application at a new site. In this case, when I attempt to initiate the connection, I get the following error message:
Can't Open Quickbooks. Quickbooks can't start because it is already running. Only Quickbooks Accountant and Quickbooks Enterprise can open more than one company file.
Since my application is trying to access the same company file that is already open, this message is misleading. Looking into the QBSDKLog.txt, I find the following:
20131010.152314 I 5324 RequestProcessor ========= Started Connection =========
20131010.152314 I 5324 RequestProcessor Request Processor, QBXMLRP2 v11.0
20131010.152314 I 5324 RequestProcessor Connection opened by app named 'IOS Briefcase Sync'
20131010.152314 I 5324 RequestProcessor OS: Microsoft Windows 7 Professional Service Pack 1 (build 7601), 32-bit
20131010.152314 I 5324 RequestProcessor Current Process is elevated
20131010.152314 I 5324 RequestProcessor Current User is in AdminGroup
20131010.152314 I 5324 RequestProcessor Current Process is ran as Admin
20131010.152314 I 5324 RequestProcessor Current Process Integrity Level : 3000
20131010.152314 I 5324 RequestProcessor Getting the IUnknown COM instance of QB
20131010.152514 E 5324 RequestProcessor An internal error occured while looking for a running instance of QuickBooks and getting its COM reference. Cannot continue. hr = 80080005
20131010.152514 E 5324 RequestProcessor Could not find or create an instance of QuickBooks using InstanceFinder hr = 8004041c
20131010.152514 I 5324 RequestProcessor Connection closed by app named 'IOS Briefcase Sync'
20131010.152514 I 5324 RequestProcessor ========== Ended Connection ==========
Any idea what might be causing the COM errors?
I had a similar problem, was getting the "Can't Open Quickbooks. Quickbooks can't start because it is already running." error.
In some situations I was also getting "If the QuickBooks company data file is not open, a call to the BeginSession method must include the name of the data file." when QuickBooks definitely did have a data file open.
I finally traced it down to the QBINSTANCEFINDER17.INI file (C:\ProgramData\INTUIT\QuickBooks\QBINSTANCEFINDER17.INI). I cleared the entries in this file and everything now works.
QuickBooks uses the QBINSTANCEFINDER ini file to keep track of open instances. Apparently when a QBW32.exe process gets shut down abnormally, entries in this file are not always
cleared as they should be. Usually that doesn't cause problems but can in certain circumstances.
EDIT: Comment...
I have also discovered that there must be a security token problem (or something similar) at work in some situations. On a Windows 7 64-bit system I've found that I cannot access QuickBooks from my application when running it under control of a debugger (Delphi 2007). However, the same .EXE file, if copied to its normal installation folder beneath Program Files (x86) when run can access QuickBooks just fine.
Otherwise (run from the debugger, or even just from my development folder) what always happens is that the running QuickBooks instance is not detected and the QBXML calls cause a 2nd instance of QuickBooks to be started, resulting in the errors you describe.
I have a Delphi application server that I installed on windows server 2008 R2
I have registered the dcom object in windows component services.
when I connect to the app server via tsocketconnection i can connect fine no problems whatsoever, and my client application runs fine.
When I try connect to the application server via Twebconnection,
I get a error :
"method not allowed error"
I have added a scripts virtual directory in iis 7.5 and added httpsrvr.dll into that directory
But still cant get it to connect from the client.