Connecting to QB 13 with QBSDK 12 gives qb_utils.js error popup - quickbooks

QB 13.0 Enterprise introduced an issue in our environment that did not exist in QB 12.0.
Using QBSDK 12.0, qbXML version 4.0, Windows Server 2008 R2 and a solution developed in python 2.7.3. QB File Doctor does not report any problems and all XMLs are successfully validated by the QB XML Validator.
I had to go thru this post to resolve the LGB file corruption issue after the upgrade:Automatic Login Failure
I have created a test .Net program to replicate the problem, which occurs at random points between BeginSession and EndSession calls:
using QBXMLRP2Lib;
RequestProcessor2 proc = new RequestProcessor2();
proc.OpenConnection2("Test QB", "Test QB", QBXMLRPConnectionType.localQBD);
string ticket = proc.BeginSession("the path to the QB file", QBFileMode.qbFileOpenMultiUser);
proc.EndSession(ticket);
proc.CloseConnection();
A "Script Error" dialog box pops up with:
Line: 46
Char: 8
Error: Unspecified error.
Code: 0
URL: https://qbinproduct.intuit.com/ipd/common/js/qb_utils.js
And the standard two options whether to continue to run the script or not.
Regardless of what is chosen, QB crashes with:
Problem signature:
Problem Event Name: APPCRASH
Application Name: qbw32.exe
Application Version: 23.0.4005.2305
Application Timestamp: 50d6cc51
Fault Module Name: StackHash_5b31
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec49b8f
Exception Code: c0000374
Exception Offset: 000ce6c3
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 5b31
Additional Information 2: 5b3188f7410a3a5d99b8b3c79d62fc31
Additional Information 3: 38e7
Additional Information 4: 38e72e11a56a600df179c0b7bdb3159c
I'll appreciate any solutions or suggestions.

Related

Unable to connect Netapp (8.1.4P1 7-Mode) with jdk1.8.0_181

We have below security configuration at storage side (8.1.4P1 7-Mode)
Configurations
tls.enable on
ssl.enable on
ssl.v2.enable off
ssl.v3.enable off
We tried to access storage using NetApp Manageability SDK 5.7 and it is working fine with jdk1.8.0_161.
We upgrade JDK to jdk1.8.0_181 and then we are not able to access it, Its throwing Exception
`2018-08-03 05:06:27,071 [Thread-1469] app-ERROR-javax.net.ssl.SSLException: Connection has been shutdown: `javax.net.ssl.SSLHandshakeException`: Received fatal alert: handshake_failure at` `sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1551)`
at sun.security.ssl.AppInputStream.read(AppInputStream.java:95)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:71)
at netapp.manage.http.HTTPMessage.readLine(HTTPMessage.java:245)
at netapp.manage.http.HTTPResponse.read(HTTPResponse.java:74)
at netapp.manage.http.HTTPClient.doRequest(HTTPClient.java:772)
at netapp.manage.NaServer.invokeHTTP(NaServer.java:955)
As per release notes of jdk "jdk1.8.0_181", JDK 181 disabled "3DES cipher suites".
Is there any way to fix it from NetApp side ?
While not an answer to the direct question of how to solve this from the NetApp side, the problem can be overcome on the application side by removing "3DES_EDE_CBC" from the jdk.tls.disabledAlgorithms security property at runtime. Something like:
final String JDK_TLS_DISABLED_ALGORITHMS = "jdk.tls.disabledAlgorithms";
final String TRIPLE_DES_EDE_CBC = "3DES_EDE_CBC";
final String disabledAlgorithms = Splitter.on(',').trimResults()
.splitToList(Security.getProperty(JDK_TLS_DISABLED_ALGORITHMS)).stream()
.filter(algo -> !algo.equals(TRIPLE_DES_EDE_CBC)).collect(joining(", "));
Security.setProperty(JDK_TLS_DISABLED_ALGORITHMS, disabledAlgorithms);

Quickfixj rejecting incoming message with "Tag appears more than once" where there is no repeated tag

Quickfixj is rejecting the following logon message:
8=FIXT.1.1|9=163|35=A|34=77086|1128=9|49=XXxVENUExXX|56=XXxUSxXX|52=20140704-11:24:22.308|108=4|98=0|1137=9|789=78069|58=RFA:f718fdb8-2ed3-4e0b-965f-4305188d06f9|1409=0|1407=100|10=013|
The actual log entry for it is:
20140704-11:24:22.316 ERROR [QFJ Message Processor] quickfixj.errorEvent - FIXT.1.1:XXxUSxXX->XXxVENUExXX: Rejecting invalid message: quickfix.FieldException: Tag appears more than once, field=1407: 8=FIXT.1.1^A9=184^A35=A^A34=77086^A49=XXxVENUExXX^A52=20140704-11:24:22.308^A56=XXxUSxXX^A1128=9^A58=RFA:f718fdb8-2ed3-4e0b-965f-4305188d06f9^A98=0^A108=4^A553=USRC^A554=test234^A789=7806 9^A1137=9^A1407=100^A1409=0^A10=093^A
Tag 1407 doesn't appear more than once though. We're using Quickfixj 1.5.3. With a FIX Version 5.0 SP2 - EP100 data dictionary. I can't see any issues with the data dictionary entries. The Logon message fields are all flat (except for the optional MsgTypeGrp which is not being used). Have tried with ValidateFieldsOutOfOrder as both Y and N. Config entries are:
[DEFAULT]
ConnectionType=initiator
HeartBtInt=4
FileStorePath=/dir/storeLoc
FileLogPath=/dir/logLoc
StartDay=sun
StartTime=09:55:00
EndDay=sun
EndTime=09:45:00
UseDataDictionary=Y
AppDataDictionary=/dir/dicLoc/QuickFIX_EP100.xml
TransportDataDictionary=/dir/dicLoc/QuickFIX_EP100.xml
ValidateFieldsOutOfOrder=N
EnableNextExpectedMsgSeqNum=Y
# Only the SP2 version supported
DefaultApplVerID=9
DefaultApplExtID=100
BeginString=FIXT.1.1
TargetCompID=XXxVENUExXX
TargetSubID=XXxSUBxXX
# Endpoint
SocketConnectHost=xxx.xxx.xxx.xxx
SocketConnectPort=XXXXX
[SESSION]
SenderCompID=XXxUSxXX
SenderLocationID=XXxLocxXX
Anyone have any ideas what could cause this. It couldn't be because there is '1407' in today's date?

Diagnosing Worklight 6 SQL Adapter issue, JPA tracing

Worklight Studio 6, SQL adapter attempting connection to DB2 database.
Standard pattern for procedure
return WL.Server.invokeSQLStatement({
preparedStatement : listUnassignedWorkOrders,
parameters : []
});
When I invoke my procedure I see this error
[ERROR ] FWLSE0035E: Invocation of procedure 'SqlStatement' failed.
[project Infrabel01] Type 'Function' currently does not support
marshalling to JSON.
And the logs show
[err] 0 WorklightPU WARN [Scheduled Executor-thread-1]
openjpa.Runtime - An error occurred while registering a
ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root
URL
[file:/C:/djna-nobackup/Workspaces/WL6.0/01/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar].
The error has been consumed. To see it, set your openjpa.Runtime log
level to TRACE. Load-time class transformation will not be available.
How to diagnose? How would I set the trace level in worklight?
JPA docs say:
property name="openjpa.Log" value="DefaultLevel=WARN, Runtime=INFO,
Tool=INFO, SQL=TRACE"
But where to put that in worklight?
The WorklightPU WARN in the log is not relevant and has been removed in newer releases of Worklight.
For your actual issue, see the following developerWorks threads with the same issue that was resolved.
Type 'Function' currently does not support marshalling to JSON.
developerWorks thread #1
developerWorks thread #2

Spectre error messages

I get the follow error messages running the
Dart Spectre example "line_primitive":
Invalid CSS property name: -webkit-touch-callout
Invalid CSS property name: flex-direction
Internal error:
'package:polymer/polymer_element.dart':
Error: line 140 pos 27: identifier 'mdv.bindModel' cannot be resolved
Timer.run(() => mdv.bindModel(root, this));
I downloaded and ran the example as is with no modifications.
Thanks
This is a known issue with the current (as of August 6th 2013) release of polymer and the SDK. The next release will include a fix for this. In the meantime you can download a nightly build http://www.dartlang.org/tools/editor/

F# SqlDataConnection TypeProvider not working with Sql Server Ce

I'am playing around with the new F# type providers in VS 11 Beta in Win 8 CP and I can't convince the SqlDataConenction type provider to work with a SqlCe database. The code:
open System
open System.Data
open System.Data.Linq
open System.Data.SqlServerCe
open Microsoft.FSharp.Data.TypeProviders
open Microsoft.FSharp.Linq
type dbSchema = SqlDataConnection<"Data Source=C:\Test\Test.sdf">
The database exists and was created using the VS11 dialog Server Explorer/Data Connections/Add New Connection/Sql Server CE/Create. No matter what I try I always get the following error:
The type provider
'Microsoft.FSharp.Data.TypeProviders.DesignTime.DataProviders'
reported an error: Error reading schema. Error : Cannot open
'C:\Test\Test.sdf'. Provider 'System.Data.SqlServerCe.3.5' not
installed.
What I've tried so far:
installed the Sql Server Ce 3.5, but the error is still the same.
modified the connection string & added a matching reference to the project:
"Provider=System.Data.SqlServerCe.3.5;Data Source=C:\Test\Test.sdf"
"Provider=System.Data.SqlServerCe.4.0;Data Source=C:\Test\Test.sdf"
I know this question was asked few years ago, but for future ref:
[<Literal>]
let connection_string =#"Data Source=C:\Test\Test.sdf"
type dbSchema = SqlDataConnection<connection_string>

Resources