web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / eConnect Problem - ...
Microsoft Dynamics GP (Archived)

eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

(0) ShareShare
ReportReport
Posted on by RedSoxFred 115

Hi.. First time poster.. I searched for a solution to the problem i have but couldnt find anything.

 

I have a pretty straight question

 I use eConnect (10.0.0.0)

 

to create a taIVTransactionHeaderInsert  with over 1000 lines of details.

This solution has worked well for a couple of years.

However, when  calling eConnect.eConnect_EntryPoint using a relatively large sXML file (over 500,000 characters in length)

I get the following exception

 "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

after a couple of minutes.

nothing else is called between the error and the EntryPoint call.. 

Can anyone tell me what's going on ?

 Thanks

 

 

 

 

 

 

 

*This post is locked for comments

I have the same question (0)
  • Jeganeedhi Krishnan Profile Picture
    Jeganeedhi Krishnan 2,500 on at
    Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

     Hi,

    Your XML file contain some error. due to big file it does not able to log in Event log.

    You can try to get the eConnect Exception using "eConnectException "(try.....Catch exp As eConnectException ) and write in txt file.

     

    Regards

    Jeganeedhi

     


  • RedSoxFred Profile Picture
    RedSoxFred 115 on at
    Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

     Thanks for the answer.

     

    I should have put more code in my example

      Try
                    res = _
                        eConnect.eConnect_EntryPoint(cs, EnumTypes.ConnectionStringType.SqlClient, strXML, _
                                                      EnumTypes.SchemaValidationType.None)
                Catch ex As eConnectException

    My first catch is for a eConnectException.  but the error throw is not of that type, therefore it goes to the last ExceptionHandler, which is the default Exception.

     

    Also I should point out that the source of the xml, when split in pieces, works, so all the pieces, taken in smaller lots, seem to work

     

  • sandipdjadhav Profile Picture
    sandipdjadhav 18,306 on at
    Re: Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

    Hello,

    Can you please check in your event Viewer any error for eConnect it will help you to understand.  In Dynamics GP webService with SQL 2005 for Sales Transaction I saw issue if line item for single Transaction is more than 2500 and Microsoft recommend us/client to go for SQL2008 , temporary client split Line Items for two Invoice.

    Let us know what you see in event Viewer I think that will help you to resolve issue.

    Thanks
    Sandip

  • RedSoxFred Profile Picture
    RedSoxFred 115 on at
    Re: Re: Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

     THanks for your help.

     

    however nothing goes in the event viewer... the error message is telling us it cant put the error in the event viewer since its too long

  • sandipdjadhav Profile Picture
    sandipdjadhav 18,306 on at
    Re: Re: Re: Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

    Can you split transaction and see you can import data ?

    Thanks
    Sandip

  • RedSoxFred Profile Picture
    RedSoxFred 115 on at
    Re: Re: Re: Re: Re: eConnect Problem - "Log entry string is too long. A string written to the event log cannot exceed 32766 characters."

     yeah when i split into more manageable groups.. lets say 250 lines of details... it works

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans