Community
New topic that came up.
I just notice while doing testing etc. The ****.pst.syncLogs logs suddenly increase the size drastically.
From average of 500mb - 2gb per day for the past 5-6days suddenly the day after increase to 100gb - 200+gb and my HDD capacity became full.
Any Idea why it happen?
Regards,
Jay
I had the same thing happening to me. No idea why it was happening. I opened a ticket with axigen and their support guys built another version of the outlook connector for me to try.
Unfortunately the customer I had that actually had the issue left and I never had the chance to actually test it.
The outlook connector though allowed you to keep only X amount of days of logs in order to keep it from filling up your hard drive.
I’m glad to see someone else having this issue as well. As much as it sucks, I’m happy to know that it’s not just an isolated issue of my own on my own infrastructure.
Maybe there is something similar in terms of infrastructure that you and I share that’s causing the issues? Axigen Host OS type, axigen version, hypervisor type, back end storage ( nfs / lvm / zfs), or client side OS / outlook versions.
I know that it’s supposed to be released with this option moving forward. If that’s the case then you should be good. I don’t know if there is an KBase article or not for this yet.
If I can, I’ll share the solution with you with the other outlook connector that was made available to me to you with the solution. This would be up to axigen to allow me to do so in case the connector is pre-release. I don’t want to step on any toes.
The work around does help, but it doesn’t solve the problem of why outlooks logs file are growing so big so fast and filling the hard drive on windows.
I think we don’t have similarities on the Infrastructure.
I am using Centos 6.11, Axigen 10.2.2.58, Standalone Server, Lvm. Client side Win10 Outlook 2016.
With Axigen Outlook connector 10.2.2.95.
I am still under testing before to put it on deployment the new version they send 10.2.2.96 for X amout of days of logs.
But the thing is we need to find answer why logs sudden increase drastically without any changes.
Yes. Completely different architecture. Same outlook connector though.
It would be very good to figure out why this is happening. Since most people seem to use outlook the connector really needs to be stable and capable and it seems that it’s missing that right now.
Like I said in my previous post, I am happy to send over the instructions on how to change this woth a link to outlook connector that was made for this issue but I would need Axigen’s permission on this to do so.
It also stems down to why this is happening and how do we resolve this issue for existing and new clients
Hello,
Thank you for your messages.
We confirm that in the last versions we gradually added more log lines in order to better investigate possible issues.
But as mentioned before Outlook Connector 10.2.2.96 comes with the registry option to delete the logs after you close outlook or after a specific number of days.
Thank you,
Bogdan Maxim
Currently we are using 10.2.2.96 as you said. But it did not do any difference.
10-20 Users access the same Email Account using Axigen Outlook Connector for collaboration etc.
Even with 1 day log delete still does not prevent the problem occupying all the free storage on the harddrives / storage.
When it happen the logs continuously increase per hour until you notice that you don’t have any free space anymore. The only thing you can do to stop it on writing big logs and cut the trend is to exit Outlook and kill on process the Window host process run32.dll 32bit.
This issue does not encounter by everyone all at the same time. But randomly to X no. of users (Big logs will start writing all the same time to this X no. of users.
Hope you can give us answer as it may lead us to break with our customers.
Regards,
JAy
Also additionally attached is the Security Logs with some abnormality maybe to help to resolve this issue.
The Security Logging continues as soon the abnormality in increase of LOGS (GB’s) start.
After it starts putting logs back the logs of Outlook connector became normal again when we see 5 request from specific IP with 1 OLK_UNSUPPORTED and 4 OLK_2016.
(Due to GDPR guidelines the Domain has been replaced by ***)
Line 446: 2020-06-20 19:29:38 +0400 02 AdminPC SECURITY:IMAP;0007D234;10.0.91.16;3860;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 447: 2020-06-20 19:29:40 +0400 02 AdminPC SECURITY:IMAP;0007D236;10.0.91.16;3863;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 448: 2020-06-20 19:29:40 +0400 02 AdminPC SECURITY:IMAP;0007D237;10.0.91.16;3865;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 449: 2020-06-20 19:29:40 +0400 02 AdminPC SECURITY:IMAP;0007D238;10.0.91.16;3867;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 450: 2020-06-20 19:29:41 +0400 02 AdminPC SECURITY:IMAP;0007D23A;10.0.91.16;3872;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 451: 2020-06-20 19:29:42 +0400 02 AdminPC SECURITY:IMAP;0007D23B;10.0.91.16;3874;OP_OK;Operations@*******.com;00005141;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 462: 2020-06-20 19:30:19 +0400 02 AdminPC SECURITY:IMAP;0007D245;10.0.91.16;3905;OP_OK;Operations@*******.com;00007a18;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 463: 2020-06-20 19:30:20 +0400 02 AdminPC SECURITY:IMAP;0007D246;10.0.91.16;3907;OP_OK;Operations@*******.com;00007a18;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 464: 2020-06-20 19:30:20 +0400 02 AdminPC SECURITY:IMAP;0007D247;10.0.91.16;3909;OP_OK;Operations@*******.com;00007a18;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 473: 2020-06-20 19:31:49 +0400 02 AdminPC SECURITY:IMAP;0007D256;10.0.91.16;3930;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 474: 2020-06-20 19:31:50 +0400 02 AdminPC SECURITY:IMAP;0007D257;10.0.91.16;3932;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 475: 2020-06-20 19:31:50 +0400 02 AdminPC SECURITY:IMAP;0007D258;10.0.91.16;3934;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 476: 2020-06-20 19:31:50 +0400 02 AdminPC SECURITY:IMAP;0007D259;10.0.91.16;3937;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 477: 2020-06-20 19:31:50 +0400 02 AdminPC SECURITY:IMAP;0007D25A;10.0.91.16;3939;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 478: 2020-06-20 19:31:50 +0400 02 AdminPC SECURITY:IMAP;0007D25B;10.0.91.16;3941;OP_OK;Operations@*******.com;0000f286;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 492: 2020-06-20 19:33:40 +0400 02 AdminPC SECURITY:IMAP;0007D270;10.0.91.16;3977;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 493: 2020-06-20 19:33:41 +0400 02 AdminPC SECURITY:IMAP;0007D271;10.0.91.16;3979;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 494: 2020-06-20 19:33:41 +0400 02 AdminPC SECURITY:IMAP;0007D272;10.0.91.16;3981;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 495: 2020-06-20 19:33:41 +0400 02 AdminPC SECURITY:IMAP;0007D273;10.0.91.16;3983;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 496: 2020-06-20 19:33:41 +0400 02 AdminPC SECURITY:IMAP;0007D274;10.0.91.16;3985;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 497: 2020-06-20 19:33:41 +0400 02 AdminPC SECURITY:IMAP;0007D275;10.0.91.16;3987;OP_OK;Operations@*******.com;0000faa3;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 528: 2020-06-20 19:37:19 +0400 02 AdminPC SECURITY:IMAP;0007D29E;10.0.91.14;61130;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 529: 2020-06-20 19:37:20 +0400 02 AdminPC SECURITY:IMAP;0007D29F;10.0.91.14;61132;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 530: 2020-06-20 19:37:20 +0400 02 AdminPC SECURITY:IMAP;0007D2A0;10.0.91.14;61134;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 532: 2020-06-20 19:37:21 +0400 02 AdminPC SECURITY:IMAP;0007D2A2;10.0.91.14;61138;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 533: 2020-06-20 19:37:21 +0400 02 AdminPC SECURITY:IMAP;0007D2A3;10.0.91.14;61140;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 534: 2020-06-20 19:37:21 +0400 02 AdminPC SECURITY:IMAP;0007D2A4;10.0.91.14;61142;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 539: 2020-06-20 19:37:35 +0400 02 AdminPC SECURITY:IMAP;0007D2A9;10.0.91.14;61151;OP_OK;Operations@*******.com;00007f39;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 558: 2020-06-20 19:41:27 +0400 02 AdminPC SECURITY:IMAP;0007D2D5;10.0.91.13;50092;OP_OK;Operations@*******.com;00000c7d;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 559: 2020-06-20 19:41:28 +0400 02 AdminPC SECURITY:IMAP;0007D2D6;10.0.91.13;50093;OP_OK;Operations@*******.com;00000c7d;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 560: 2020-06-20 19:41:28 +0400 02 AdminPC SECURITY:IMAP;0007D2D7;10.0.91.13;50094;OP_OK;Operations@*******.com;00000c7d;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 572: 2020-06-20 19:42:34 +0400 02 AdminPC SECURITY:IMAP;0007D2EB;10.0.91.13;50098;OP_OK;Operations@*******.com;000084e3;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 608: 2020-06-20 19:44:16 +0400 02 AdminPC SECURITY:IMAP;0007D312;10.0.91.13;50130;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 609: 2020-06-20 19:44:17 +0400 02 AdminPC SECURITY:IMAP;0007D313;10.0.91.13;50131;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 610: 2020-06-20 19:44:21 +0400 02 AdminPC SECURITY:IMAP;0007D314;10.0.91.13;50132;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 611: 2020-06-20 19:44:21 +0400 02 AdminPC SECURITY:IMAP;0007D315;10.0.91.13;50133;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 612: 2020-06-20 19:44:22 +0400 02 AdminPC SECURITY:IMAP;0007D316;10.0.91.13;50134;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 613: 2020-06-20 19:44:26 +0400 02 AdminPC SECURITY:IMAP;0007D317;10.0.91.13;50136;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 743: 2020-06-20 20:18:13 +0400 02 AdminPC SECURITY:IMAP;0007D3C7;10.0.91.11;50830;OP_OK;Operations@*******.com;0000e766;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 836: 2020-06-20 20:44:18 +0400 02 AdminPC SECURITY:IMAP;0007D432;10.0.91.13;50322;OP_OK;Operations@*******.com;00004325;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 1602: 2020-06-21 00:29:12 +0400 02 AdminPC SECURITY:IMAP;0007D81F;10.0.91.23;60103;OP_OK;Operations@*******.com;0000491a;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1614: 2020-06-21 00:30:13 +0400 02 AdminPC SECURITY:IMAP;0007D82B;10.0.91.23;60105;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1615: 2020-06-21 00:30:14 +0400 02 AdminPC SECURITY:IMAP;0007D82C;10.0.91.23;60107;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1616: 2020-06-21 00:30:14 +0400 02 AdminPC SECURITY:IMAP;0007D82D;10.0.91.23;60109;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1617: 2020-06-21 00:30:14 +0400 02 AdminPC SECURITY:IMAP;0007D82E;10.0.91.23;60111;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1618: 2020-06-21 00:30:14 +0400 02 AdminPC SECURITY:IMAP;0007D82F;10.0.91.23;60113;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1619: 2020-06-21 00:30:14 +0400 02 AdminPC SECURITY:IMAP;0007D830;10.0.91.23;60115;OP_OK;Operations@*******.com;0000c984;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1646: 2020-06-21 00:35:15 +0400 02 AdminPC SECURITY:IMAP;0007D86C;10.0.91.23;60135;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1647: 2020-06-21 00:35:16 +0400 02 AdminPC SECURITY:IMAP;0007D86D;10.0.91.23;60137;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1648: 2020-06-21 00:35:16 +0400 02 AdminPC SECURITY:IMAP;0007D86E;10.0.91.23;60139;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1649: 2020-06-21 00:35:17 +0400 02 AdminPC SECURITY:IMAP;0007D86F;10.0.91.23;60141;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1650: 2020-06-21 00:35:17 +0400 02 AdminPC SECURITY:IMAP;0007D870;10.0.91.23;60143;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1651: 2020-06-21 00:35:17 +0400 02 AdminPC SECURITY:IMAP;0007D871;10.0.91.23;60145;OP_OK;Operations@*******.com;00009107;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1667: 2020-06-21 00:40:08 +0400 02 AdminPC SECURITY:IMAP;0007D88F;10.0.91.24;55534;OP_OK;Operations@*******.com;0000d36b;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_2016;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Line 1672: 2020-06-21 00:40:47 +0400 02 AdminPC SECURITY:IMAP;0007D894;10.0.91.185;49860;OP_OK;Operations@*******.com;00002c5c;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1673: 2020-06-21 00:40:47 +0400 02 AdminPC SECURITY:IMAP;0007D895;10.0.91.185;49862;OP_OK;Operations@*******.com;00002c5c;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1674: 2020-06-21 00:40:47 +0400 02 AdminPC SECURITY:IMAP;0007D896;10.0.91.185;49864;OP_OK;Operations@*******.com;00002c5c;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1676: 2020-06-21 00:40:50 +0400 02 AdminPC SECURITY:IMAP;0007D898;10.0.91.185;49872;OP_OK;Operations@*******.com;00002c5c;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1677: 2020-06-21 00:40:50 +0400 02 AdminPC SECURITY:IMAP;0007D899;10.0.91.185;49874;OP_OK;Operations@*******.com;00002c5c;Axigen Outlook Connector 10.2.2 (build 96.0);cache on;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18363), 64-bit;Authentication successful;
Line 1687: 2020-06-21 00:43:24 +0400 02 AdminPC SECURITY:IMAP;0007D8A3;10.0.91.24;50323;OP_OK;Operations@*******.com;0000b920;Axigen Outlook Connector 10.2.2 (build 96.0);cache off;OLK_UNSUPPORTED;OLK 32-bit;Microsoft (build 18362), 64-bit;Authentication successful;
Hi Jay,
Please note that the logs you showed are not IMAP logs but these are Security protocol logs and dispplay login attempts and their status.
Regarding the Outlook Connector log size, you may change the value to 0 and this way the logs will be deleted every time the client is closing Outlook Connector.
Thank you.
Bogdan Maxim
Yeah it is the Security Logs.
The thing that I notice in this log is when one (IP / Machine) that makes multiple and continues request connection and with OLK_UNSUPPORTED is the one that makes the BIG LOGS.
And the machine that works properly and have SMALL LOGS make request connection once only. With OLK_2016.
Maybe this is the problem we are looking for.
Why other have OLK_UNSUPPORTED and Others show properly OLK_2016?
All machine are same setups.
I can do 0 value. But then some customers does not even close Outlook.
Or if they close outlook after filling up the harddisk capacity, Outlook will not open unless you kill microsoft outlook at process and windows host process run32.dll 32bit. Even after deletion of logs automatically or manually.
Regards,
Jay
No more asnwers? Still I got alot of queries about this Axigen Outlook Connector and I need answers. Because since we shifted from IMAP to Outlook Connector it gives us a lot of problem.
Hello Jay,
Thank you for your response.
Do note that we do not answer on this forum as fast as we answer on support tickets and therefore please note that there might be periods of time when you will not receive a rapid answer. We anyway try to answer here as well as soon as possible.
Regarding the registry option set to 0 after checking with our developers, we know that as soon as you set it to 0, delete the old logs and start Outlook, there shouldn’t be any OLK logs written any longer.
Regarding the OLK_UNSUPPORTED behavior, in order to further investigate this, please attach to your response an awrhive with this type of BIG LOGS so our developers can further investigate it.
Do note that as soon as we download that archive from our side the attachment will be deleted due to the fact that you have private information there.
Also note that for any new Outlook / Outlook Connector queries you may always open new topics - if the discussion is not directly related to the size of sync logs.
Thank you.
Bogdan Maxim