Reset Password · YAF.NET Support Forum

Welcome Guest! To enable all features please Login or Register

Posted by: OrdinaryNimda - Tuesday, 19 July 2022 11:22:25
[b]UPGRADE to 3.16 fails after successful Install Extension[/b] All 5 steps of the upgrade are done OK, no error in output. But when finalizing, there is this error message - see image link below. (I checked upload parameters and the filesize limit for upload is 30MB, so this is not the error cause. Also, the Windows Server Search is disabled on this machine. And WTF "please check your internet connection"?) [b]The DNN website with the forum remains in an unstable state, so I have to restore to an older version[/b] (backed up all the the web-site files plus the DNN database. It takes just a few minutes, so no problem). I can supply some additional error events from the database if it would help. [attach]2264[/attach]

Posted by: OrdinaryNimda - Tuesday, 19 July 2022 11:22:25

[b]UPGRADE to 3.16 fails after successful Install Extension[/b] All 5 steps of the upgrade are done OK, no error in output. But when finalizing, there is this error message - see image link below. (I checked upload parameters and the filesize limit for upload is 30MB, so this is not the error cause. Also, the Windows Server Search is disabled on this machine. And WTF "please check your internet connection"?) [b]The DNN website with the forum remains in an unstable state, so I have to restore to an older version[/b] (backed up all the the web-site files plus the DNN database. It takes just a few minutes, so no problem). I can supply some additional error events from the database if it would help. [attach]2264[/attach]

Posted by: tha_watcha - Wednesday, 20 July 2022 12:47:02
I updated the release [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6113[/url] Issue is fixed now, also a few other dnn related issues. [quote]And WTF "please check your internet connection"?)[/quote] This message is a standard dnn error message.

Posted by: OrdinaryNimda - Thursday, 21 July 2022 14:15:57
I did this 6113 version a few times, but I cannot get it to work in a forum function. Install goes thru, and the forum software starts, but the DNN personaBar AND all static images are Error 500. So I have to do a restore SQL database + restore the file system. I also tried doing this with a different skin - XCILLION latest version. Same error: successful YAF Module 6113 install, but on restarting the web, the same errors were seen (No DNN PersonaBar for Host AND static images error 500, prolly JS files error also). Same symptoms as a custom skin error. There are quite a few start-up errors, when the forum starts, in the DNN Event Log file, dealing with this: [b]Microsoft.AspNet.Identity.Owin[/b]. But this is also in version 3.12.6105, I checked now. I have to revert back to this old version, so that the forum works. There are some forum errors, which remain and were fixed in later YAF version (ctrl-V not working in editor, blank page after adding a forum post), but everything is running, and DNN server security is working. EXAMPLE of one of the errors of DNN portal startup: [code=markup] 2022-07-21 14:01:25,933 [Sandy-Bridge][Thread:14][ERROR] DotNetNuke.Web.DependencyInjectionInitialize - Unable to configure services for pdfbox-1.8.9, Version=1.8.9.0, Culture=neutral, PublicKeyToken=null, see exception for details - LoaderException: Could not load file or assembly 'IKVM.OpenJDK.Core, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'IKVM.OpenJDK.SwingAWT, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'junit, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'fontbox-1.8.9, Version=1.8.9.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.Assembly.GetTypes() at DotNetNuke.DependencyInjection.Extensions.TypeExtensions.SafeGetTypes(Assembly assembly, ILog logger) [/code]

Posted by: OrdinaryNimda - Thursday, 21 July 2022 14:15:57

I did this 6113 version a few times, but I cannot get it to work in a forum function. Install goes thru, and the forum software starts, but the DNN personaBar AND all static images are Error 500. So I have to do a restore SQL database + restore the file system. I also tried doing this with a different skin - XCILLION latest version. Same error: successful YAF Module 6113 install, but on restarting the web, the same errors were seen (No DNN PersonaBar for Host AND static images error 500, prolly JS files error also). Same symptoms as a custom skin error. There are quite a few start-up errors, when the forum starts, in the DNN Event Log file, dealing with this: [b]Microsoft.AspNet.Identity.Owin[/b]. But this is also in version 3.12.6105, I checked now. I have to revert back to this old version, so that the forum works. There are some forum errors, which remain and were fixed in later YAF version (ctrl-V not working in editor, blank page after adding a forum post), but everything is running, and DNN server security is working. EXAMPLE of one of the errors of DNN portal startup: [code=markup] 2022-07-21 14:01:25,933 [Sandy-Bridge][Thread:14][ERROR] DotNetNuke.Web.DependencyInjectionInitialize - Unable to configure services for pdfbox-1.8.9, Version=1.8.9.0, Culture=neutral, PublicKeyToken=null, see exception for details - LoaderException: Could not load file or assembly 'IKVM.OpenJDK.Core, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'IKVM.OpenJDK.SwingAWT, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'junit, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. - LoaderException: Could not load file or assembly 'fontbox-1.8.9, Version=1.8.9.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.Assembly.GetTypes() at DotNetNuke.DependencyInjection.Extensions.TypeExtensions.SafeGetTypes(Assembly assembly, ILog logger) [/code]

Posted by: tha_watcha - Thursday, 21 July 2022 14:27:22
Can you post the errors related to the Microsoft.AspNet.Identity.Owin dll? or better upload the entire event log text file ([b]currentdate.log.resources[/b]) from the folder [b]Portals\_default\Logs[/b]

Posted by: OrdinaryNimda - Friday, 22 July 2022 09:19:57
I saved a new DNN LOG, going from restarted 3.13 IIS service, doing 3.16 Extension upgrade and clicking one or two pages after the successful upgrade. There are some other errors besides Owin, and I think NOT all are YAF Module related. And they also appear in the 3.13 part of the LOG. (EDITED)

Posted by: tha_watcha - Friday, 22 July 2022 11:50:14
Only the [b]System.Web.Http.dll[/b] entry and the [b]System.Web.Http.WebHost.dll[/b] entries are relevant. can you check the web.config if there entries for these dlls under runtime/dependentAssembly

Posted by: OrdinaryNimda - Friday, 22 July 2022 12:33:33
I checked, there are no such entries in the web.config at the root web folder of the DNN istallation, or in any subfolder, or any other folder on the machine. (These two entries do not exist in web.config files: System.Web.Http.dll and System.Web.Http.WebHost.dll) The files [b]System.Web.Http.dll[/b] and [b]System.Web.Http.WebHost.dll[/b] do exist in about 8 folders, each of the same dates and sizes everywhere.

Posted by: OrdinaryNimda - Friday, 22 July 2022 12:33:33

I checked, there are no such entries in the web.config at the root web folder of the DNN istallation, or in any subfolder, or any other folder on the machine. (These two entries do not exist in web.config files: System.Web.Http.dll and System.Web.Http.WebHost.dll) The files [b]System.Web.Http.dll[/b] and [b]System.Web.Http.WebHost.dll[/b] do exist in about 8 folders, each of the same dates and sizes everywhere.

Posted by: tha_watcha - Friday, 22 July 2022 15:23:47
Okay then it can't work. In all my test installations the entries exist, very odd. I updated the module again, now the entries are created. Also the search function is working again. [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6114[/url]

Posted by: OrdinaryNimda - Friday, 22 July 2022 16:40:30
(There is an UPDATE on the bottom of this msg) I did the upgrade, everything went OK ...But on IIS restart it is the same effects: personaBar gone, images invalid and also none of those System.Web DLL entries in web.config. If you want, I can send the DNN LOG, but it looks the same as before (with current timestamps). I see they are part of .NET 4.8... and they are on the machine in the proper folder, and also in the main dotnetnuke BIN folder. Maybe this will interest you: i did NOT upgrade YAF from 2.1xx until 3.12 or 3.13. Maybe there is some functionality still missing? [b]UPDATE[/b]: I checked all DNN LOG files, the problems started on 9 march 2022 - there were no such errors before (only a few font errors, and some foolish hacking attempts). On 9 March 2022 was probably when I upgraded from 2.1xx to 3.12 ... that's when those functinality errors started showing up, and the LOG files are big with many errors, such as above. Obviously the upgrade did not succeed with everything needed. I definitely did upgrade to DNN 9.10.02 before upgrading YAF, which I upgraded some days later.

Posted by: OrdinaryNimda - Friday, 22 July 2022 16:40:30

(There is an UPDATE on the bottom of this msg) I did the upgrade, everything went OK ...But on IIS restart it is the same effects: personaBar gone, images invalid and also none of those System.Web DLL entries in web.config. If you want, I can send the DNN LOG, but it looks the same as before (with current timestamps). I see they are part of .NET 4.8... and they are on the machine in the proper folder, and also in the main dotnetnuke BIN folder. Maybe this will interest you: i did NOT upgrade YAF from 2.1xx until 3.12 or 3.13. Maybe there is some functionality still missing? [b]UPDATE[/b]: I checked all DNN LOG files, the problems started on 9 march 2022 - there were no such errors before (only a few font errors, and some foolish hacking attempts). On 9 March 2022 was probably when I upgraded from 2.1xx to 3.12 ... that's when those functinality errors started showing up, and the LOG files are big with many errors, such as above. Obviously the upgrade did not succeed with everything needed. I definitely did upgrade to DNN 9.10.02 before upgrading YAF, which I upgraded some days later.

Posted by: tha_watcha - Friday, 22 July 2022 16:57:57
What happens when you manually add the missing entries in the web.config... [code=markup] <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" /> </dependentAssembly> [/code] and [code=markup] <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" /> </dependentAssembly> [/code] in the node /configuration/runtime/

Posted by: tha_watcha - Friday, 22 July 2022 16:57:57

What happens when you manually add the missing entries in the web.config... [code=markup] <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" /> </dependentAssembly> [/code] and [code=markup] <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" /> </dependentAssembly> [/code] in the node /configuration/runtime/

Posted by: OrdinaryNimda - Friday, 22 July 2022 17:11:41
Correction, I do have this in the old version of web.config: (this was my mistake, I searched wrong, with [b]DLL in the string System.Web.Http.DLL[/b]) So, I have the node with 5.2.7.0: [code=markup]<bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" />[/code] UPDATE: The upgrade to 3.1.6 did this, and I think this is what you wanted. [code=markup] <!--<bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" />--> <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" />[/code] So I checked this on the upgraded to 3.16, and web.config was updated properly by the Extension framework. The functionality is not upgraded, so I have to go back to 3.13... where we have [b]oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0"[/b]. This looks OK with respect to web.config in both versions. One more correction: my "old" version of YAF is [b]3.12.6105[/b], this is for YAF Module and for YAF What's new. The new ones show as [b]3.16.51[/b] and [b]3.15.51[/b] respectively in Extension installer.

Posted by: OrdinaryNimda - Friday, 22 July 2022 17:11:41

Correction, I do have this in the old version of web.config: (this was my mistake, I searched wrong, with [b]DLL in the string System.Web.Http.DLL[/b]) So, I have the node with 5.2.7.0: [code=markup]<bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" />[/code] UPDATE: The upgrade to 3.1.6 did this, and I think this is what you wanted. [code=markup]  <bindingRedirect oldVersion="0.0.0.0-5.2.9.0" newVersion="5.2.7.0" xmlns="urn:schemas-microsoft-com:asm.v1" />[/code] So I checked this on the upgraded to 3.16, and web.config was updated properly by the Extension framework. The functionality is not upgraded, so I have to go back to 3.13... where we have [b]oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0"[/b]. This looks OK with respect to web.config in both versions. One more correction: my "old" version of YAF is [b]3.12.6105[/b], this is for YAF Module and for YAF What's new. The new ones show as [b]3.16.51[/b] and [b]3.15.51[/b] respectively in Extension installer.

Posted by: tha_watcha - Saturday, 23 July 2022 17:52:43
Okay i try a different approach by updating the dlls directly [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6114[/url] You can attach the log file as zip directly here in the editor, in case there is still an error.

Posted by: OrdinaryNimda - Monday, 25 July 2022 16:36:14
I tried 6115 now, however it FAILS when updating the Extension (red bar on top says error, like we had before with 6113). I have the LOG file, deleted all entries before TIME 16:21, so this started the IIS, after which I did the Extension update in DNN. Please take note it is running on 6113 until the failed extension upgrade. (The web does not start after the upgrade, so am doing RESTORE, copying all 6113 files to the web, and restoring the SQL database. Now back again on 6113) There are some DNN DLL entries with errors in the LOG, which are unrelated to YAF. I deleted those unused DLLs from the /bin folder, but not yet from wherever they are referenced (old extensions, which were deleted from the Extensions, and still referenced by DNN for some reason). Also, I changed the SKIN of the YAF Module to "YAF", so there should be no more skin errors due to responsive. [attach]2265[/attach]

Posted by: OrdinaryNimda - Monday, 25 July 2022 16:36:14

I tried 6115 now, however it FAILS when updating the Extension (red bar on top says error, like we had before with 6113). I have the LOG file, deleted all entries before TIME 16:21, so this started the IIS, after which I did the Extension update in DNN. Please take note it is running on 6113 until the failed extension upgrade. (The web does not start after the upgrade, so am doing RESTORE, copying all 6113 files to the web, and restoring the SQL database. Now back again on 6113) There are some DNN DLL entries with errors in the LOG, which are unrelated to YAF. I deleted those unused DLLs from the /bin folder, but not yet from wherever they are referenced (old extensions, which were deleted from the Extensions, and still referenced by DNN for some reason). Also, I changed the SKIN of the YAF Module to "YAF", so there should be no more skin errors due to responsive. [attach]2265[/attach]

Posted by: OrdinaryNimda - Thursday, 28 July 2022 12:38:05
There was also one YAF error in the CKEditor provider (I have two folders): ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3 ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1 I took 2 folders from the 4.5.3 plugin folder, and copied them to the 4.15.1 plugin folder. Then, there was no more "newsarticleslinks" and "iframe" errors (in HTMLEditor on the DNN page, which uses YAF.WhatsNew). So these two folder were copied from: [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\iframe[/b] [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\newsarticlelinks[/b] They were copied here, and everything now works on 6113 (which I will try to upgrade with 6116 again later): [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1\plugins\[/b] I do not know if this is a misconfig error, or only YAF Module upgrade error from 2 years ago. I usually do not delete files from working installations. I hope this helps somewhat!

Posted by: OrdinaryNimda - Thursday, 28 July 2022 12:38:05

There was also one YAF error in the CKEditor provider (I have two folders): ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3 ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1 I took 2 folders from the 4.5.3 plugin folder, and copied them to the 4.15.1 plugin folder. Then, there was no more "newsarticleslinks" and "iframe" errors (in HTMLEditor on the DNN page, which uses YAF.WhatsNew). So these two folder were copied from: [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\iframe[/b] [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\newsarticlelinks[/b] They were copied here, and everything now works on 6113 (which I will try to upgrade with 6116 again later): [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1\plugins\[/b] I do not know if this is a misconfig error, or only YAF Module upgrade error from 2 years ago. I usually do not delete files from working installations. I hope this helps somewhat!

Posted by: tha_watcha - Thursday, 28 July 2022 13:32:41
[quote=OrdinaryNimda;73421]There was also one YAF error in the CKEditor provider (I have two folders): ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3 ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1 I took 2 folders from the 4.5.3 plugin folder, and copied them to the 4.15.1 plugin folder. Then, there was no more "newsarticleslinks" and "iframe" errors (in HTMLEditor on the DNN page, which uses YAF.WhatsNew). So these two folder were copied from: [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\iframe[/b] [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\newsarticlelinks[/b] They were copied here, and everything now works on 6113 (which I will try to upgrade with 6116 again later): [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1\plugins\[/b] I do not know if this is a misconfig error, or only YAF Module upgrade error from 2 years ago. I usually do not delete files from working installations. I hope this helps somewhat![/quote] Those issues have nothing to do with YAF. This are issues of the DNNConnect CKEditor Provider. YAF dont use the editor provider

Posted by: tha_watcha - Thursday, 28 July 2022 13:32:41

[quote=OrdinaryNimda;73421]There was also one YAF error in the CKEditor provider (I have two folders): ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3 ..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1 I took 2 folders from the 4.5.3 plugin folder, and copied them to the 4.15.1 plugin folder. Then, there was no more "newsarticleslinks" and "iframe" errors (in HTMLEditor on the DNN page, which uses YAF.WhatsNew). So these two folder were copied from: [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\iframe[/b] [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.5.3\plugins\newsarticlelinks[/b] They were copied here, and everything now works on 6113 (which I will try to upgrade with 6116 again later): [b]..\Providers\HtmlEditorProviders\DNNConnect.CKE\js\ckeditor\4.15.1\plugins\[/b] I do not know if this is a misconfig error, or only YAF Module upgrade error from 2 years ago. I usually do not delete files from working installations. I hope this helps somewhat![/quote] Those issues have nothing to do with YAF. This are issues of the DNNConnect CKEditor Provider. YAF dont use the editor provider

Posted by: tha_watcha - Thursday, 28 July 2022 15:36:59
I did some further testing looks like updating the dlls directly doesnt work. I updated the module again now it references the same dlls as dnn. [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6116[/url]

Posted by: OrdinaryNimda - Thursday, 28 July 2022 18:35:43
[quote=tha_watcha;73422][quote=OrdinaryNimda;73421]There was also one YAF error in the CKEditor provider (I have two folders): ... EDITED for BREVITY[/quote] Those issues have nothing to do with YAF. This are issues of the DNNConnect CKEditor Provider. YAF dont use the editor provider[/quote] I use the HTML module (which references this CKEditor.Provider), on the Hompage where I read YAF.WhatsNew, and the provider JS scripts were referencing newsarticlelinks, and that is how I found the error. This is cleaned up now. On the "forum" page with the YAF Module, there are no YAF errors, so everything is looking good. 👍 [quote=tha_watcha;73423]I did some further testing looks like updating the dlls directly doesnt work. I updated the module again now it references the same dlls as dnn. https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6116[/quote]I will try this later tonight CET time, or tomorrow and will report back as soon as possible.

Posted by: OrdinaryNimda - Thursday, 28 July 2022 18:35:43

[quote=tha_watcha;73422][quote=OrdinaryNimda;73421]There was also one YAF error in the CKEditor provider (I have two folders): ... EDITED for BREVITY[/quote] Those issues have nothing to do with YAF. This are issues of the DNNConnect CKEditor Provider. YAF dont use the editor provider[/quote] I use the HTML module (which references this CKEditor.Provider), on the Hompage where I read YAF.WhatsNew, and the provider JS scripts were referencing newsarticlelinks, and that is how I found the error. This is cleaned up now. On the "forum" page with the YAF Module, there are no YAF errors, so everything is looking good. 👍 [quote=tha_watcha;73423]I did some further testing looks like updating the dlls directly doesnt work. I updated the module again now it references the same dlls as dnn. https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6116[/quote]I will try this later tonight CET time, or tomorrow and will report back as soon as possible.

Posted by: OrdinaryNimda - Thursday, 28 July 2022 19:24:29
I did the update. I get the personaBar error 500 again, as for all other static files (JPG, JS, etc). The UPDATE procedure DOES go thru with no errors and the Extension is loaded successfully. I see 3.16.6116 in the Extensions for both YAF modules. Also, there is no fatal crash on the pages now, only the static files are not visible. So something is not having a correct assembly binding in web.config. I am supplying the LOG file, update started at TIME 18:50 ... and I restarted the web twice, did a few clicks on pages, with all those entries being from version 3.16.6116. [attach]2266[/attach] [b]EDIT: [/b]I also made a copy of the [b]web.config [/b]ver 6116, I can send the whole relevant [b][runtime][/b] node, if it would help.

Posted by: OrdinaryNimda - Thursday, 28 July 2022 19:24:29

I did the update. I get the personaBar error 500 again, as for all other static files (JPG, JS, etc). The UPDATE procedure DOES go thru with no errors and the Extension is loaded successfully. I see 3.16.6116 in the Extensions for both YAF modules. Also, there is no fatal crash on the pages now, only the static files are not visible. So something is not having a correct assembly binding in web.config. I am supplying the LOG file, update started at TIME 18:50 ... and I restarted the web twice, did a few clicks on pages, with all those entries being from version 3.16.6116. [attach]2266[/attach] [b]EDIT: [/b]I also made a copy of the [b]web.config [/b]ver 6116, I can send the whole relevant [b][runtime][/b] node, if it would help.

Posted by: tha_watcha - Friday, 29 July 2022 09:56:29
Another day, another version [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6117[/url] Issues from the log should be resolved. But you should also resolve the issues of the missing assemblies and also remove or update the Aricie.PortalKeeper module

Posted by: OrdinaryNimda - Friday, 29 July 2022 11:17:48
There is a package installation error, with 2 errors near the very end of the file (one SQL duplicate insertion and one javascript bundle; the ACL permissions on the webserver folders are FULL control for SYSTEM and NETv4.5, as is specified by DNN). The Extension remains now in version 6115, according to the Extension manager. [attach]2268[/attach] - contains resource error log, and the output from extension manager. (INFO on the errors in the resource LOG: I deleted Aricie and two other DLLs now. They were in the \BIN folder for some reason, after uninstalling or upgrading those extensions a long time ago. I have no idea why DNN tries to load them, because they are not referenced in web.config, or used in any way. Maybe I did a bad restore from backup 5 years ago...)

Posted by: OrdinaryNimda - Friday, 29 July 2022 11:17:48

There is a package installation error, with 2 errors near the very end of the file (one SQL duplicate insertion and one javascript bundle; the ACL permissions on the webserver folders are FULL control for SYSTEM and NETv4.5, as is specified by DNN). The Extension remains now in version 6115, according to the Extension manager. [attach]2268[/attach] - contains resource error log, and the output from extension manager. (INFO on the errors in the resource LOG: I deleted Aricie and two other DLLs now. They were in the \BIN folder for some reason, after uninstalling or upgrading those extensions a long time ago. I have no idea why DNN tries to load them, because they are not referenced in web.config, or used in any way. Maybe I did a bad restore from backup 5 years ago...)

Posted by: tha_watcha - Sunday, 31 July 2022 11:50:38
Updated manifest, installer should work again [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url]

Posted by: OrdinaryNimda - Sunday, 31 July 2022 19:22:45
The installation WORKED - no errors, no warnings, and after refreshing pages (Forum DNN Module, and one with Forum DNN What's New), everything looked better. The PersonaBar worked too. But after restart of the web server service (and later restarted the whole machine to be sure), the same kind of startup error occurrs as before, no PersonaBar, and static files are not available. Wil restore version back to the one that was working. This is the LOG after restarting: [attach]2269[/attach] [b]EDIT:[/b] This is informational, now back on the previous working version. The DNN Extension manager lists 3.16.6115 as the version for YAF.Model and 3.15.6115 as YAF.WhatsNew. Also, pressing F12 in Chrome, there are no Javascript errors on any of the pages with the YAF module nor on the ones with only DNN.

Posted by: OrdinaryNimda - Sunday, 31 July 2022 19:22:45

The installation WORKED - no errors, no warnings, and after refreshing pages (Forum DNN Module, and one with Forum DNN What's New), everything looked better. The PersonaBar worked too. But after restart of the web server service (and later restarted the whole machine to be sure), the same kind of startup error occurrs as before, no PersonaBar, and static files are not available. Wil restore version back to the one that was working. This is the LOG after restarting: [attach]2269[/attach] [b]EDIT:[/b] This is informational, now back on the previous working version. The DNN Extension manager lists 3.16.6115 as the version for YAF.Model and 3.15.6115 as YAF.WhatsNew. Also, pressing F12 in Chrome, there are no Javascript errors on any of the pages with the YAF module nor on the ones with only DNN.

Posted by: tha_watcha - Tuesday, 2 August 2022 12:37:24
Updated the module again [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url] But i guess its still not working

Posted by: OrdinaryNimda - Wednesday, 3 August 2022 08:49:11
This is the same file size as the previous 6118? Will try now, first backup, and then upgrade and testing...

Posted by: OrdinaryNimda - Wednesday, 3 August 2022 15:06:21
I tried it now, there are 3 errors at installation of the Extension. After restarting IIS, the DNN app does not start due to an ASPX error. Restoring old version... Providing the Log file + Package Installation Report: [attach]2270[/attach] (The forum runs on the previous working version, so as far as I am concerned, this can wait and it is not a priority.)

Posted by: tha_watcha - Wednesday, 3 August 2022 15:33:40
There was a wrong / at the end. update downloads again [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url] Installation was successfull on my fresh new dnn installation.

Posted by: OrdinaryNimda - Wednesday, 3 August 2022 17:37:44
Install went 100% success. After restarting IIS and the second time the whole machine, there appears to be no data. In the LOG it said Guest user does not exist. This is probably a small error, so I made a backup copy of that SQL database, just in case if it might help. (EDIT: there is also the PersonaBar not showing error) I am restoring the old forum version. Here is the DNN Log: [attach]2271[/attach]

Posted by: OrdinaryNimda - Wednesday, 3 August 2022 17:37:44

Install went 100% success. After restarting IIS and the second time the whole machine, there appears to be no data. In the LOG it said Guest user does not exist. This is probably a small error, so I made a backup copy of that SQL database, just in case if it might help. (EDIT: there is also the PersonaBar not showing error) I am restoring the old forum version. Here is the DNN Log: [attach]2271[/attach]

Posted by: tha_watcha - Thursday, 4 August 2022 14:04:35
I think i found the issue, updated module again... [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url]

Posted by: OrdinaryNimda - Thursday, 4 August 2022 15:54:29
Tried it now, it is the same as v3 6118 yesterday: success install, but on restart there are errors, NoPersonaBar and empty forum WhatsNew and no topics. [b]You might find this usefull: [/b]when restoring back to the old version, I restored the old filesystem and forgot to restore the SQL from backup. In the Extension manager it said 6118 for the YAF extension versions and the forum worked and everything looked OK. So old files, but new SQL with 6118. Now I restored the forum back to the old version including the SQL. I don't want to mess anything up to make new problems. (If you need the resource LOG, I will send it, it has the same Guest user error as yesterday.)

Posted by: OrdinaryNimda - Thursday, 4 August 2022 15:54:29

Tried it now, it is the same as v3 6118 yesterday: success install, but on restart there are errors, NoPersonaBar and empty forum WhatsNew and no topics. [b]You might find this usefull: [/b]when restoring back to the old version, I restored the old filesystem and forgot to restore the SQL from backup. In the Extension manager it said 6118 for the YAF extension versions and the forum worked and everything looked OK. So old files, but new SQL with 6118. Now I restored the forum back to the old version including the SQL. I don't want to mess anything up to make new problems. (If you need the resource LOG, I will send it, it has the same Guest user error as yesterday.)

Posted by: tha_watcha - Thursday, 4 August 2022 16:28:07
I don't think I can't fix that. I tested 4 different dann installations and can't reproduce the errors. Can you post your web.config after the install? Does the forum show data as guest user?

Posted by: OrdinaryNimda - Friday, 5 August 2022 11:29:45
[quote=tha_watcha;73438]I don't think I can't fix that. I tested 4 different dann installations and can't reproduce the errors. Can you post your web.config after the install? Does the forum show data as guest user?[/quote]I am providing web-configs (before/after install v3_6118), and only changed the SQL password to "XXXXX". [attach]2272[/attach] I just found and fixed one error: in the [b]\DesktopModules\YetAnotherForumDotNet\langues\[/b] folder I made a copy of the file [b]english.xml[/b] into [b]english - Copy.xml [/b]... (there must be a reference to it somewhere) and now there is no more PersonaBar error after v3_6118. (EDIT: I can confirm this behavior even after IIS Service re-start, so this is good.) However, after the upgrade, the YAF database "looks empty" with the text [i]"Currently the Forum doesnt contain any Messages." [/i]for the YAF.WhatsNew module on the first page, and is totally empty on any of the YAF.Module pages[i]. [/i]This is for all users Guest, Normal, and also Host.. (EDIT: I restored everything back to the old version, including the SQL, just in case.)

Posted by: OrdinaryNimda - Friday, 5 August 2022 11:29:45

[quote=tha_watcha;73438]I don't think I can't fix that. I tested 4 different dann installations and can't reproduce the errors. Can you post your web.config after the install? Does the forum show data as guest user?[/quote]I am providing web-configs (before/after install v3_6118), and only changed the SQL password to "XXXXX". [attach]2272[/attach] I just found and fixed one error: in the [b]\DesktopModules\YetAnotherForumDotNet\langues\[/b] folder I made a copy of the file [b]english.xml[/b] into [b]english - Copy.xml [/b]... (there must be a reference to it somewhere) and now there is no more PersonaBar error after v3_6118. (EDIT: I can confirm this behavior even after IIS Service re-start, so this is good.) However, after the upgrade, the YAF database "looks empty" with the text [i]"Currently the Forum doesnt contain any Messages." [/i]for the YAF.WhatsNew module on the first page, and is totally empty on any of the YAF.Module pages[i]. [/i]This is for all users Guest, Normal, and also Host.. (EDIT: I restored everything back to the old version, including the SQL, just in case.)

Posted by: tha_watcha - Friday, 5 August 2022 11:44:22
i updated the module again.. [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url] another fix attempt I see that one user has in the yaf_User table the language file english - copy.json in the column LanguageFile. Change it to english.json or create the file in the languages folder.

Posted by: OrdinaryNimda - Friday, 5 August 2022 12:20:31
I tried it, and have the same error situation, with no YAF data in the WhatsNew and YAF forum module. now SQL: [b]yaf_User[/b] table has the column [b]LanguageFile [/b]with [b]NULL[/b] values for ALL users, before and after upgrade. I will check the file system for references to "english - copy". (EDIT: no text files contain this; I will check the file [b]yafdnn-res.zip.manifest[/b] on the next upgrade, I confirm it is not there in the previous version, only english.xml). Also, there would be the unresolved [b]popper.js[/b] error, so I added this as HTML markup to the [b]default.aspx[/b] so it works without JS errors until this issue is resolved. [b][script src="https://unpkg.com/@popperjs/core@2"][/script][/b]

Posted by: OrdinaryNimda - Friday, 5 August 2022 12:20:31

I tried it, and have the same error situation, with no YAF data in the WhatsNew and YAF forum module. now SQL: [b]yaf_User[/b] table has the column [b]LanguageFile [/b]with [b]NULL[/b] values for ALL users, before and after upgrade. I will check the file system for references to "english - copy". (EDIT: no text files contain this; I will check the file [b]yafdnn-res.zip.manifest[/b] on the next upgrade, I confirm it is not there in the previous version, only english.xml). Also, there would be the unresolved [b]popper.js[/b] error, so I added this as HTML markup to the [b]default.aspx[/b] so it works without JS errors until this issue is resolved. [b][script src="https://unpkg.com/@popperjs/core@2"][/script][/b]

Posted by: tha_watcha - Friday, 5 August 2022 12:47:18
[quote]SQL: yaf_User table has the column LanguageFile with NULL values for ALL users, before and after upgrade. I will check the file system for references to "english - copy". (EDIT: no text files contain this; I will check the file yafdnn-res.zip.manifest on the next upgrade, I confirm it is not there in the previous version, only english.xml).[/quote]Then the setting is in the HostSettings yaf_Registry table under Name = language, Value = 'english - copy.json' [quote]I tried it, and have the same error situation, with no YAF data in the WhatsNew and YAF forum module. now[/quote] It seems there is something wrong with the yaf table. I assume the ActiveAcess table is empty after you load the page with the Whats New module or the Forum Module. Would it be possible to send me all yaf_xxx tables as exported sql file to my mail address [email]support@yetanotherforum.net[/email]? So i can check the data and reproduce the issue.

Posted by: tha_watcha - Friday, 5 August 2022 12:47:18

[quote]SQL: yaf_User table has the column LanguageFile with NULL values for ALL users, before and after upgrade. I will check the file system for references to "english - copy". (EDIT: no text files contain this; I will check the file yafdnn-res.zip.manifest on the next upgrade, I confirm it is not there in the previous version, only english.xml).[/quote]Then the setting is in the HostSettings yaf_Registry table under Name = language, Value = 'english - copy.json' [quote]I tried it, and have the same error situation, with no YAF data in the WhatsNew and YAF forum module. now[/quote] It seems there is something wrong with the yaf table. I assume the ActiveAcess table is empty after you load the page with the Whats New module or the Forum Module. Would it be possible to send me all yaf_xxx tables as exported sql file to my mail address [email]support@yetanotherforum.net[/email]? So i can check the data and reproduce the issue.

Posted by: OrdinaryNimda - Friday, 5 August 2022 12:51:37
Yes, I will send everything, give me some time., maybe half and hour so. [b]EDIT: [/b]yaf_Registry DOES contain a [b]Name = 'language' [/b]and [b]value = 'english - Copy.xml'[/b] row. [code=markup]RegistryID Name Value BoardID 5 language english.xml NULL 10 language english - Copy.xml 1[/code] [b]EDIT:[/b] the SQL db locale is "slovenian". So i will export to UNICODE. However, it can also be english or german, or whatever you will specify, if this is not OK.

Posted by: OrdinaryNimda - Friday, 5 August 2022 12:51:37

Yes, I will send everything, give me some time., maybe half and hour so. [b]EDIT: [/b]yaf_Registry DOES contain a [b]Name = 'language' [/b]and [b]value = 'english - Copy.xml'[/b] row. [code=markup]RegistryID Name Value BoardID 5 language english.xml NULL 10 language english - Copy.xml 1[/code] [b]EDIT:[/b] the SQL db locale is "slovenian". So i will export to UNICODE. However, it can also be english or german, or whatever you will specify, if this is not OK.

Posted by: tha_watcha - Friday, 5 August 2022 14:00:55
I seemed to have compiled the wrong package. Updated version again.. [url]https://github.com/YAFNET/YAFNET-DNN/releases/tag/v3.1.6-6118[/url]

Posted by: OrdinaryNimda - Friday, 5 August 2022 14:56:47
This is interesting now! 1) Install 100% success. 2) Restarting IIS... 3) There IS forum content on YAF.WhatsNew and YAF.Forum modules!! Clicking YAF.WhatsNew goes to the proper forum message. This is good... 😁 4) However, now PersonaBar is not working, bootstrap, jquery and other JS errors are the source of error, images are not visible. (I deleted the reference to Popper.JS from the popper server, but it does not change behavior. In the previous version, referencing Popper.js helped to clear all JS errors.) I will do what you ask here. (I have tried fiddling with the sql data export and I can do it, but will need more time. Either manually exporting data for each yaf_Table, which I can do, or SQL Notebook for a notebook file. This is because I only have the SQL Express version, no wizard for multiple tables export. On the other hand, I can send you the whole DNN database, if it would be easier for you. But I think the database part of YAF is now operational.)

Posted by: OrdinaryNimda - Friday, 5 August 2022 14:56:47

This is interesting now! 1) Install 100% success. 2) Restarting IIS... 3) There IS forum content on YAF.WhatsNew and YAF.Forum modules!! Clicking YAF.WhatsNew goes to the proper forum message. This is good... 😁 4) However, now PersonaBar is not working, bootstrap, jquery and other JS errors are the source of error, images are not visible. (I deleted the reference to Popper.JS from the popper server, but it does not change behavior. In the previous version, referencing Popper.js helped to clear all JS errors.) I will do what you ask here. (I have tried fiddling with the sql data export and I can do it, but will need more time. Either manually exporting data for each yaf_Table, which I can do, or SQL Notebook for a notebook file. This is because I only have the SQL Express version, no wizard for multiple tables export. On the other hand, I can send you the whole DNN database, if it would be easier for you. But I think the database part of YAF is now operational.)

Posted by: tha_watcha - Friday, 5 August 2022 15:55:50
Okay if the forum shows up, then you don't need to send me the data. It's likely an js issue. Are you have any js issues in the browser console? Did you try to clear the browser cache or reload the page via ctrl+ F5?

Posted by: OrdinaryNimda - Friday, 5 August 2022 16:26:58
Before, I forgot about "english - Copy.xml", if is still referenced in the new version. Later today I will do the update Extension proc again and check this explicitely. However, in the prev versions, manual insertion of [b]Popper.js[/b] into [b]default.aspx[/b] solved all JS problems, now it does not... Will report back today or later.

Posted by: OrdinaryNimda - Friday, 5 August 2022 18:35:50
[b]UPDATE #2:[/b] The forum runs normally with SQL database on [b]v5_6118[/b], but with old files (6113...). Extension says 6118 in the Extension manager, but the files are 6113. (One example, DELETE MESSAGE dow not work in that version, which you fixed some time ago. The editor shows "AUTOSAVE" in green on the client area, etc. But it does not run with 6118 files. The PersonaBar does not work and the static elements are invalid/missing. Of course I tried deleting all cached web file elements, the F12 console shows the same error 500 errors. (I did not know, that POPPER is part of the bootstrap library until now.) So, there is a faulty reference somewhere in the files. Of course this does not mean, that it is because of YAF, the error could be originating from anywhere, as far as I know my Math. I also made a copy of "[b]english - Copy.json[/b]", but it does not change anything. I have to restore the old working version, because PersonaBar must be running for Admin or Host. If I get new ideas to test, I will do the Extension update again. It only takes a few minutes to restore the old version. Thank heavens this is a very small website forum (except for the millions of search engines).

Posted by: OrdinaryNimda - Friday, 5 August 2022 18:35:50

[b]UPDATE #2:[/b] The forum runs normally with SQL database on [b]v5_6118[/b], but with old files (6113...). Extension says 6118 in the Extension manager, but the files are 6113. (One example, DELETE MESSAGE dow not work in that version, which you fixed some time ago. The editor shows "AUTOSAVE" in green on the client area, etc. But it does not run with 6118 files. The PersonaBar does not work and the static elements are invalid/missing. Of course I tried deleting all cached web file elements, the F12 console shows the same error 500 errors. (I did not know, that POPPER is part of the bootstrap library until now.) So, there is a faulty reference somewhere in the files. Of course this does not mean, that it is because of YAF, the error could be originating from anywhere, as far as I know my Math. I also made a copy of "[b]english - Copy.json[/b]", but it does not change anything. I have to restore the old working version, because PersonaBar must be running for Admin or Host. If I get new ideas to test, I will do the Extension update again. It only takes a few minutes to restore the old version. Thank heavens this is a very small website forum (except for the millions of search engines).

Posted by: tha_watcha - Saturday, 6 August 2022 13:27:31
Does the personabar doesnt work on all pages? If it is a javascript issue then the issue would occur only on the pages with the yaf module and the yaf whats new module on. Otherwise there would be an error logged to the log files. Yaf does indeed load the bootstrap libary inluding popper. But the default theme in dnn loads an older bootstrap libary. If both are loaded then its causing trouble. As i wrote before the correct way would be to load the libary in the theme via the client resource management api as i wrote here... [url]https://yetanotherforum.net/forum/Posts/m73302-Errors-upgrading-to-3-13[/url]

Posted by: tha_watcha - Saturday, 6 August 2022 13:27:31

Does the personabar doesnt work on all pages? If it is a javascript issue then the issue would occur only on the pages with the yaf module and the yaf whats new module on. Otherwise there would be an error logged to the log files. Yaf does indeed load the bootstrap libary inluding popper. But the default theme in dnn loads an older bootstrap libary. If both are loaded then its causing trouble. As i wrote before the correct way would be to load the libary in the theme via the client resource management api as i wrote here... [url]https://yetanotherforum.net/forum/Posts/m73302-Errors-upgrading-to-3-13[/url]

Posted by: OrdinaryNimda - Sunday, 7 August 2022 10:50:16
Yes, I implemented those changes at the time. Switching to one of the newest YAF skins (YAF) solved the problem. And deleted all older skins and also updated the 3rd party skin ascx files with the directives you gave. 👍 Since then, there are no more Javascript problems in the "current old version". There is no errors or severe warnings on any pages with WhatsNew and YafModule on the working version. I have found a great utility WinMerge for folder comparisons. There is something interfering with the newest version, maybe even a "typo" somewhere. This does not mean that the source is YAF, it could be from anywhere. If I find anything relevant, I will inform you here. The goal is to have the YAF Module running on 6118 which has great improvements.

Posted by: OrdinaryNimda - Sunday, 7 August 2022 10:50:16

Yes, I implemented those changes at the time. Switching to one of the newest YAF skins (YAF) solved the problem. And deleted all older skins and also updated the 3rd party skin ascx files with the directives you gave. 👍 Since then, there are no more Javascript problems in the "current old version". There is no errors or severe warnings on any pages with WhatsNew and YafModule on the working version. I have found a great utility WinMerge for folder comparisons. There is something interfering with the newest version, maybe even a "typo" somewhere. This does not mean that the source is YAF, it could be from anywhere. If I find anything relevant, I will inform you here. The goal is to have the YAF Module running on 6118 which has great improvements.

Posted by: tha_watcha - Sunday, 7 August 2022 11:44:44
Sorry but at this point i cant help you, if you keep mixing up versions. If there are no more javascript errors, and the personabar didnt work on all dnn pages then the issue is likly caused by a depending assembly reference in the web.config. Are there are anymore issues in the log files? You can also access the files which throw an 500 error in the browser console. directly via url to see the error

Posted by: tha_watcha - Sunday, 7 August 2022 11:44:44

Sorry but at this point i cant help you, if you keep mixing up versions. If there are no more javascript errors, and the personabar didnt work on all dnn pages then the issue is likly caused by a depending assembly reference in the web.config. Are there are anymore issues in the log files? You can also access the files which throw an 500 error in the browser console. directly via url to see the error

Posted by: OrdinaryNimda - Sunday, 7 August 2022 12:04:33
You have done the upgrade 100% for the YAF part of the forum software. And I thank you for that! I have just found there is one bootstrap.min.css.map warning [b]on a page, that has no YAF component[/b]. So not YAF dependent error at all. And that stems from doing DNN upgrades. I only fiddle with the presentation layer of the website, so ASCX and maybe some CSS. Or include CSS styles directly in ASCX, so there is no fiddling with JS at all, including the boostrap libraries. I wouldn't touch that with a 10-foot barge-pole, let alone a debugger.😁 I will notify here if I succeed in cleaning up the errors. Maybe it can help other users on DNN.

Posted by: OrdinaryNimda - Sunday, 7 August 2022 12:04:33

You have done the upgrade 100% for the YAF part of the forum software. And I thank you for that! I have just found there is one bootstrap.min.css.map warning [b]on a page, that has no YAF component[/b]. So not YAF dependent error at all. And that stems from doing DNN upgrades. I only fiddle with the presentation layer of the website, so ASCX and maybe some CSS. Or include CSS styles directly in ASCX, so there is no fiddling with JS at all, including the boostrap libraries. I wouldn't touch that with a 10-foot barge-pole, let alone a debugger.😁 I will notify here if I succeed in cleaning up the errors. Maybe it can help other users on DNN.

Important Information: