Developer forum

Hi Terri

Will look into this. Can you add the PDB (debugging symbols) files for Ecommerce.dll for a day and post the error again? That would give a line number and ease debugging.

Thanks, Nicolai

Thanks Nicolai. How do we get the proper pdb for the Ecommerce.dll? https://doc.dynamicweb.com/downloads/other-downloads/developer/debugging-symbols doesn't seem to have it for 9.4.11...

Hi Imar

I have the debugging symbols on that list, see dump #1. Also they can be found in the myGet feed as well.

Also find them attached.

BR Nicolai

Sorry, I could have been more clear. Yes, the ZIP is there, but it doesn't contain a PDB for Ecommerce (see dump). Many of the 9.4 zips don't have that. Bug in the deployment process?

On NuGet I can see they only exist for the latest package. Will that still help you? Wouldn't the code, line numbers etc. be too far off?

Imar

Yes...

It appears that the zip file contains only those that is part of the build of a release. That is only Dynamicweb.Admin since 9.4

The missing pdb file from MyGet seems to be the clean-up policies... The symbols are there for versions of dlls - but not all. Hoooray for nuget packages. 1 benefit 1000 problems.

But - you also have to check which version of Dynamicweb.Ecommerce.dll you are using. It is not the same as the Dynamicweb version.

See if that version is in myget please.

9.4.11 seems to run on 1.4.39 when I look at its packages.config:

<package id="Dynamicweb.Ecommerce" version="1.4.39" targetFramework="net46" />

It exists in MyGet (https://myget.org/feed/dynamicweb-packages/package/nuget/Dynamicweb.Ecommerce/1.4.39) but without symbols.

1.4.47 (https://myget.org/feed/dynamicweb-packages/package/nuget/Dynamicweb.Ecommerce/1.4.47) is the latest with symbols.

@Terri: can we  / should we upgrade to a later version to get access to these symbols more easily?

@Imar, the dev solution is running already 9.4.15. I upgraded to see if it would fix this problem. Let's grab the symbols for that solution and we can schedule production upgrade once we have more info on the failure.

Here is the updated error after the pdb file was uploaded.

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Status>
  <StartTime Ticks="636662058029661142" Humanized="2018-07-03 09:10:02" />
  <EndTime Ticks="636662058031379857" Humanized="2018-07-03 09:10:03" />
  <Runtime>187</Runtime>
  <Count>0</Count>
  <TotalCount>0</TotalCount>
  <State>Failed</State>
  <Fail>
    <Reason>The task 'rebuild index.task' failed.</Reason>
    <ExceptionMessage>Object reference not set to an instance of an object.</ExceptionMessage>
    <ExceptionStackTrace>   at Dynamicweb.Ecommerce.Products.ProductRelatedGroup.GetRelatedGroupCollection(String query) in E:\agent\_work\72\s\05 - Modules\Dynamicweb.Ecommerce\Dynamicweb.Ecommerce-1.4\Dynamicweb.Ecommerce\Products\ProductRelatedGroup.vb:line 248
   at Dynamicweb.Ecommerce.Common.Application.GetRelatedGroups() in E:\agent\_work\72\s\05 - Modules\Dynamicweb.Ecommerce\Dynamicweb.Ecommerce-1.4\Dynamicweb.Ecommerce\Common\Application.vb:line 460
   at Dynamicweb.Ecommerce.Indexing.ProductIndexSchemaExtender.GetFields() in E:\agent\_work\72\s\05 - Modules\Dynamicweb.Ecommerce\Dynamicweb.Ecommerce-1.4\Dynamicweb.Ecommerce\Indexing\ProductIndexSchemaExtender.vb:line 116
   at Dynamicweb.Indexing.Schemas.ExtensionFieldDefinition.GetFields()
   at Dynamicweb.Indexing.IndexHelper.ConvertToIndex(XElement obj)
   at Dynamicweb.Indexing.IndexService.LoadIndex(String name)
   at Dynamicweb.Indexing.IndexHelper.BuildIndexInstances(String repository, String indexName, String buildName)
   at Dynamicweb.Indexing.Repositories.Tasks.Task.&lt;&gt;c__DisplayClass37_0.&lt;Run&gt;b__0(Tracker tracker)</ExceptionStackTrace>
  </Fail>
  <LogInformation>Failed.</LogInformation>
  <Meta />
</Status>

Hi guys,

Need to kick this dead horse. This has never been resolved and the client is reporting the failures again. Any idea on a fix?

Thanks,
Terri

Hi Terri,

I have a couple of questions

1) Which version of Dynamicweb do the solution run on now? 

2) Is it still the same stacktrace, you see in the logs? I can see, that some code has changed in 9.4, so it no longer matches the stacktrace given here in this thread

3) Has the errors been done for the last year, and have just started to come again?

Best regards,

Steffen

Hi Steffen,

The site is still running 9.4.11. The error is the same. The issue has been occuring since this was first reported.

Thanks
Terri

The upgrade to 9.4.20 resolved the failures.