Hi Dan,

I better understand now! :-) The huge number of users is the source of your problem. The Store module use standard DNN API to get the users list, then you could encounter similar problems with other modules and even DNN.

The Store module can run with different modes, one of them allow to order without having a DNN user account. In this mode, orders have to be linked to an impersonated user account defined in the Store Admin module. That's why you can't start normaly the Store Admin module, because the interface try to fill a dropdown list with user accounts to select this impersonated account.

I could try to ask for a role, then get users from the selected role to fill the dropdown list. Whatever the workaround, you could avoid this kind of problem if you try to increase the timeout value in your web.config file. By default, ASP.NET automatically kills a non responding request after 90 seconds. If your SQL Server instance is too slow because a huge db and/or a too slow server hardware then any long request will fails! Also, you should read my last blog post. I suppose that your users have been imported, then your log file could be huge and this can slow down SQL Server access!

Please give me a few days to apply the workaround (asking the role at first) and send me an email, I will send you a beta version when this will be done.

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.

Hello Gilles -

I applied the various pills from your article including:

1. dbcc shrnkdatabase

2. verified simple revoery model

3. reindexed tables

4. Cleaned up users that have not been in the system for awhile (we still have well over 100k)

5. increased the executiontimeout to 10800 in the web.config

Once the timeout was increased, they system memory was getting maxed out as well as the cpu usage. We're on a 2.4 ghz with 1mb ram. I went ahead and submitted the issue to dnn support since we're also experiencing this on the file manager. Seems like those admin pages should just default to admin users only instead of loading up all users in the system.

take it easy,

Dan

 

Hello -

We were already set to simple recovery, I did not have to modify that setting. We have separate web servers, our test environment uses a 2 ghz with 1 gb ram for the web server. The database is its own server and has 2 ghz with 4 gb ram.

name                 IsDataFile IsLogFile     size             spaceused     CurrentSizeMB     SafeSizeMB
dnn_Data             1                 0             393848         358176             3076.94             2798.25
dnn_Log               0                 1             864                 261                 6.75                     2.04

We can always throw more hardware at the problem, but it seems loading all users (160,000) into a datareader and then individually grabbing the profile data for them on a page load could be done more efficiently. For instance, on an admin page just load up admin users. I can't imagine ever going through a list of users that long would be useful? That statement is more directed at how the core dnn functionality is working, not the store :)

I might be missing something there.

 

thanks again!

Dan