Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Chilkat

Pages: 1 ... 4 5 [6] 7
76
C / C++ / Re: Chilkat and Qt - linker errors. Help!
« on: November 29, 2017, 08:39:22 AM »
Try adding the following library to the linker input files:

Code: [Select]
legacy_stdio_definitions.lib

77
When this error occurs, it mean the SMTP client (Chilkat) has completed the SMTP session (i.e. send the full MIME of the email message to the server) and is waiting for the SMTP server's final response -- but it never comes.

It may be that you need to wait longer than 30 seconds for the SMTP server to finally give a response.

One must realize that non-responsive SMTP servers happen from time to time.  For example, every once in a while, but not very often, in my day-to-day experience in replying to email using Mozilla Thunderbird, I'll experience a time where the email server (Outlook 365 in my case) just doesn't respond.  A retry solves the problem.  Chilkat as the SMTP client is in the same position as any other email client.  If the server just doesn't respond for no reason, then it could just be a temporary SNAFU on the server-side...


78
ActiveX / Re: AES256 CBC Derivation of Key + IV From Password & Salt values
« on: November 28, 2017, 09:41:54 AM »
For the case you described, the typical way it's done is to use PBKDF2 to generate enough bytes for both the secret key and the IV.  For AES256, the secret key is 256-bits (i.e. 32 bytes).  The IV is 16 bytes for AES regardless of whether it's AES256, AES128, etc.   Therefore, you would use PBKDF2 to generate 48 bytes (384 bits).

If you get the result in hex, then you would split the returned hex string in two parts -- one part for the secret key, and one part for the IV.

But you really need to know what the other system does.  Did it generate the key and IV material as I described above?  There is no "standard" for it.  Perhaps it generated the key + IV as I described, but maybe it uses the 1st 16 bytes for the IV, and the trailing bytes for the secret key, or maybe the reverse?   

79
General Discussion / Re: Xamarin+Chilkat
« on: November 20, 2017, 09:34:49 AM »

Unfortunately, it's not something that Chilkat explicitly supports at this time.   Check back in the future to see if this is still the case.

80
I found what appears to be the answer here:  https://github.com/easyphp/easyphp-devserver/issues/25

I think you need to

    Copy the chilkat_9_5_0.dll file from the php directory to the apache/bin directory
    Restart the Apache server



81
I got a problem to load your php DLL, with this configuration :

Windows Server 2012 64Bits / Apache 2.4.25 / PHP Version 7.0.17

My php.ini Extension setting is pretty simple :

extension_dir = "c:\php\ext\"

Then,

extension=chilkat_9_5_0.dll

Every extension enabled in my php.ini are loading correctly, except chilkat_9_5_0.dll

-->   PHP Warning:  PHP Startup: Unable to load dynamic library 'c:\\php\\ext\\chilkat_9_5_0.dll' - The specified module could not be found.\r\n in Unknown on line 0

The version file I used for your lib is that one : https://chilkatdownload.com/9.5.0.69/chilkat-9.5.0-php-7.0-nts-x64.zip

Thanks in advance for any help or tips on my issue!

82
REST / HTTP / HTTPS / Re: Error downloading files
« on: November 18, 2017, 12:14:46 PM »
Update to the latest version of Chilkat.

As the years go by, the external world changes.  Protocol versions are updated, new protocol features are introduced, old protocol features become deemed insecure, and as servers are updated new requirements might come into effect.  Chilkat keeps pace with these developments.  It's likely that updating to the latest version of Chilkat will resolve the problem.

In general, I believe that any software that communicates with anything over the Internet cannot remain static for many years. 

83
Ruby / Re: Using Chilkat with Bundler
« on: November 17, 2017, 09:47:20 AM »
Ah, I finally put the following in the Gemfile:

gem 'chilkat', '=9.5.0.69', :path => "vendor/cache"

and that did the trick.  Funny, I always thought that Bundler looks in vendor/cache by default, but apparently not.


84
Ruby / Re: Using Chilkat with Bundler
« on: November 17, 2017, 09:46:46 AM »
We are putting the  9.5.0.69 version into vendor/cache and forcing bundler to use it via the line

gem 'chilkat', '=9.5.0.69'

in ./Gemfile.

Then, we are getting the following error:

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    chilkat (= 9.5.0.69) was resolved to 9.5.0.69, which depends on
      ruby (~> 2.4)

85
Ruby / Using Chilkat with Bundler
« on: November 17, 2017, 09:45:52 AM »
Specifically, I can use the Ruby 2.0 version for Mac (it works very well), but when I try to do a 'bundle install' with the 1.9.3 64-bit version for Linux, Bundler complains that we need Ruby 2.4.

We deploy this (older) app on Centos using Ruby 1.9.3, and moving the app to a newer version of Ruby would be quite painful.

Am I doing something wrong with the 1.9.3 version?

86
.NET / Re: Using Mailman in vb.NET
« on: November 17, 2017, 09:38:50 AM »
There should be no limit.  It would be good to post more information, such as a code snippet, the full contents of the LastErrorText, and the contents of the SmtpSessionLog property.

87
FTP / Re: FTPS over http proxy ignoring my proxy settings
« on: November 15, 2017, 10:13:45 AM »
Thanks.  I just tested with Chilkat v9.5.0.69 and it worked fine.  Given that you're using v9.5.0.65, check to see if updating to v9.5.0.69 solves the problem.

88
Compression / Archives / Re: XML structure of LastErrorXml
« on: November 08, 2017, 10:42:39 AM »
Thanks.  This question comes up quite a bit.  People want "an exact error".  The problem is that there are innumerable "exact errors" possible.  (Granted there are common errors that might occur.)

My belief is that when only an "exact error" is provided, it typically ends up being an arcane/cryptic message or some "error code".  You see this all the time with Microsoft errors -- where one gets some undecipherable, meaningless error message and code, which provides no context or even a glimpse of understanding was to what might be the cause of the problem.  The result is that the application developer wastes an enormous amount of time in working to solve each and every error.

Chilkat wants to provide context and details so that 95% of the time, the LastErrorText/LastErrorXml already has the information to understand the cause of the problem, and what is required to fix.  If the application developer remains uncertain, then he/she can pass it to Chilkat for advice, and that usually solves the problem quickly.

For common errors, one solution is to use the code generation for XML parsing at http://tools.chilkat.io/xmlParse.cshtml    You can copy-and-paste a sample of the LastErrorXml, such as what you posted, and then generate the code that parses it.  (You'll throw out most of it and only keep the parts you want..)   For example, the code generated, in C#, to generate the LastErrorXml you provided is: 

Code: [Select]
Chilkat.Xml xml = new Chilkat.Xml();

//  Insert code here to load the above XML into the xml object.

string tagPath;
string DllDate;
string ChilkatVersion;
string UnlockPrefix;
string Architecture;
string Language;
int VerboseLogging;
string error;
int v_cMethod;
string path;

DllDate = xml.GetChildContent("Extract|DllDate");
ChilkatVersion = xml.GetChildContent("Extract|ChilkatVersion");
UnlockPrefix = xml.GetChildContent("Extract|UnlockPrefix");
Architecture = xml.GetChildContent("Extract|Architecture");
Language = xml.GetChildContent("Extract|Language");
VerboseLogging = xml.GetChildIntValue("Extract|VerboseLogging");
error = xml.GetChildContent("Extract|inflateToBaseDir|inflateMappedEntry|inflateToOutput2|mappedInflateToOutput|error");
v_cMethod = xml.GetChildIntValue("Extract|inflateToBaseDir|inflateMappedEntry|inflateToOutput2|mappedInflateToOutput|_cMethod");
error = xml.GetChildContent("Extract|inflateToBaseDir|inflateMappedEntry|error");
path = xml.GetChildContent("Extract|inflateToBaseDir|inflateMappedEntry|path");
error = xml.GetChildContent("Extract|error");

89
ActiveX / Re: google calendar delete & modify
« on: November 06, 2017, 04:53:39 PM »
The examples will appear here:  http://rest-examples.chilkat.io/default.cshtml

The tool at http://tools.chilkat.io/restCreate.cshtml is what I'll be using to create the examples, and I have the ability to one-click publish to http://rest-examples.chilkat.io/default.cshtml

It'll be a bumpy ride, as all of this is new and still partially under development.  I'm going to try to work through calendar examples... 

90
ActiveX / Re: google calendar delete & modify
« on: November 06, 2017, 04:22:09 PM »
I'm working to build examples using this tool:  http://tools.chilkat.io/restCreate.cshtml


Pages: 1 ... 4 5 [6] 7