Jump to content

chriscorcoran

Hornbill Users
  • Content Count

    356
  • Joined

  • Last visited

  • Days Won

    2

chriscorcoran last won the day on May 7 2017

chriscorcoran had the most liked content!

Community Reputation

17 Good

About chriscorcoran

  • Rank
    Senior Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,410 profile views
  1. @Steve Giller not sure if its officlally been fixed but I have switched back to csv using the latest R script and my dashboards are now updating OK. Thanks.
  2. script attached, im using minus instance and key hornbill script.txt
  3. Hi @Steve G I have given it a try today but getting error below. I noticed the report seems to be still trying to output as csv even though I selected xlsx, thanks
  4. I have gone back to the report it is using in Hornbill and when I export the csv the report is corrupt. Looks fine in preview. Are there issues with the reporting?
  5. spoke to soon getting the following when I updated the script in my source settings OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH)).
  6. My bad, typical man, hadnt read through readme, I forgot the issue of Details: "Unable to translate bytes [E2][80] at index 0 from specified code page to Unicode. is caused by UTF-8, chnaged it to ISO-8859-1 This will usually be "UTF-8", but if you have issues returning data with certain characters (the Windows E2 80* characters are the usual culprits) then choose a different character set to use, ie: "ISO-8859-1"
  7. I did notice a new script posted in git so I have tried thet but now get We encountered an error while trying to connect. Details: "Unable to translate bytes [E2][80] at index 0 from specified code page to Unicode." Tested on two seperate reports that use R and both fail with the same error.
  8. Just refreshing a report this morning and getting the following erro, nothing I know of has changed. I have set myself a new API key just in case but I still get ADO.NET: R script error. Error: Argument 'txt' must be a JSON string, URL or file. Execution halted Any ideas?
  9. Also sites are no longer picking up when raising a call. You can get the site form the list once a call has been logged. Not sure if thats the same bug?
  10. Over the last few weeks when raising a call, the customer name is not pulled through from the database. If you go back and try again it often works. You can type the name in and it finds the customer but all calls when raising show customer as blank, even when they have a record in the database. Any ideas? All users are using Chrome.
  11. thanks @Keith Stevenson yes it seemed to resolve after a few hours. Thanks
  12. Morning, anyone else getting POP3 read failure emails into Hornbill mailbox this morning? There was a problem reading mail from the POP3 account:Server: outlook.office365.comPort: 110User: Password: The error reported by the server was:ChilkatLog:FetchByMsgnum(61984ms):DllDate: May 23 2020ChilkatVersion: 9.5.0.83UnlockPrefix: HRNBLL.CBX102021Architecture: Little Endian; 64-bitLanguage: Visual C++ 2019 / x64VerboseLogging: 1Component successfully unlocked using purchased unlock code.msgnum: 1PopCmdSent: LIST 1sendCommand: Elapsed time: 0 millisecPopCmdResp: +OK 1 59356getOneLineResponse:
×
×
  • Create New...