Developer forum

I have not seen it before.

What does your browser developer toolbar reveals? Any 404s, 500s or anything? could be something not coming out of DW correctly.

NP

Hey Nicolai,

Actually i see this in my console when trying to enter my Repository.. Not able to enter my repo now

I didn't notice anything in the network tab which couldn't load etc.

See attached.

Hi again Nicolai,

I got the console error sorted - by trying to completely remove all index files and folders located in the Index folder along with the files and folders in the Repositories folder.

I am now able to create a new index, add a default ProductIndexSchemaExtender (full) and two instances (Index A and Index B). However, when I try to build the Index, it still says Data is null.

The following error code is thrown in the Log's section in the Diagnotics folder: 

 Starting processing products.
2017-10-25 18:49:50.451: Product index builder experienced a fatal error.. System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.    at System.Data.SqlClient.SqlBuffer.get_Int32()    at Dynamicweb.Ecommerce.Indexing.ProductIndexBuilder.ProcessProducts()    at Dynamicweb.Ecommerce.Indexing.ProductIndexBuilder.Build(IIndexWriter writer, Tracker tracker)
2017-10-25 18:49:50.451: Product index builder experienced a fatal error.
2017-10-25 18:49:50.451: Failed (3913 / 3941).
2017-10-25 18:49:50.451: Closing index writer.
2017-10-25 18:49:50.451: Closed index writer.

Are there more locations where index files are being saved, or something that I might miss. The above mentioned steps where to start from a fresh, with a new clean index, clean repo etc.

The repo name is the same though, but the files itself was deleted before I started obviously..

BR Mikkel

Hey Nicolai,

They are all NULL.

FYI, we don't have any variants on the solution.

DB schema says the column can be null though.

EDIT: I tried to update the column ProductVariantProdCounter to 0 on all products as we dont have variants, and now the index is being built correctly.

Though up untill a couple of days ago it worked, so im kinda confused why the index suddendly doesn't build because of this

Data is being imported, and I guess my workaround will be just to set this field to 0, as we before mentioned dont have variants :) 

Good learning though! 

Thanks Nicolai :)

BR Mikkel

So, to sum up:

Setting ProductVariantProdCounter = 0 fixed the issue.

Great. I made a change to the code to handle dbnull.

BR Nicolai

Hi Anders,

Sorry, but I marked your question as an answer..

However, if you're working with variants, my guess is that you have to set them in order for the DW backend to show variants correclty. That's obviously according to my experience - have had a lot of that stuff recently.

Let me know if you need any input on this.

BR Mikkel

Hi Mikkel

I am not working with any variants just simple products and product groups. However as a result of an import from an external system, the field is left null. 

This would normally be a problem if not for Nicolai's fix that he mentioned he made the 26th oct. So i was wondering if that fix did not make it out into a dynamicweb version since the same issue can be found in the latest version 9.3.8.

BR
Anders 

Hi Anders,

Probably not yet, Nicolai will most likely enlighten us when ever it has been fixed.

However, if you're able to set the field(s) in the import I think that would be the way to go for now.

BR Mikkel

Hi Nicolai,

I have just upgraded one of our solutions from 9.4 to the latest 9.13.9 and I got the same error.

I don't have Null ProductNames nor Null ProductVariantProdCounter.
Any other potential field to look into?

Thank you,
Adrian

In my case, I am suspecting something from order details.

I have set the index to skip order history and now it runs.

Adrian