Hi all,

We are moving the tier 1 to the tier 2 as rule base. Most of the migration of the studies seamlesly completed. But in the work que of the partition there are some error messages

object reference not set to an instance of an object

any idea / help

thanks

sinan

 

 

 

Sinan,

I'd have to see a more explicit reference from the log file to attempt to figure out what is going on with this. More than likely, however, its something data specific with the study that caused the problem. You may want to reset the WorkQueue entry or if the option is available, reprocess it and see what happens.

Steve

Steve,

As I have checked the log files, I think, the problem seems caused by the time out during th migration attempt (count is 4) to connect the databse and exception thrown.

I attached the log file for that day. The rest  and delete options are active, reprocess is not.

Thanks

sinan

Sinan,

First, I should have asked, what version of SQL are you using? Express or Standard? 2005 or 2008? Also, what version of our software are you using?

If you are using the 2.0 software, we didn't see anything similar to this in our testing, although there were some changes in how we deal with connections with the 2.0 release that may have caused us to use more connections at any one time.

Have you made any adjustments to the WorkQueueThreadCount configuration option in the ShredHostService.config file? This may have an impact. Also, there is a CommandTimeout configuration option in the ShredHostService.config file that's set to 120 seconds by default. You could experiment with setting this to a higher value to see if it addresses the issue.

Otherwise, I'm not sure why you're seeing these timeouts and other database related errors.

Steve

Hi Steve,

The sys config is win 2003 server 64 bit, SQL standart 64 bit, CCIS 1.5 I did not make any changes in the config files.

Do you think upgrade to CCIS 2 will solve the problem

thanks

sinan

Hi Sinan,

Unfortunately, its hard to say if the issue will be resolved with 2.0, since I'm not really sure what's causing the issue for you in the first place. In our testing, we've never really seen an issue like this. It seems like an issue actually with SQL Server not being able to handle the load, which doesn't really make sense given everything you've described about the system.

Sorry I can't be more of a help.

Steve

Hi Steve,

first thanks for your help,
Indeed I am not having the problem. When I checked the time period that the errors do occur the sysytem was accepting the studies from two sources, importing studies from one of the partitions import directory. Do ypu think if this might cause the overload, and the errors?. Im not sure but the only explanation seems that. The hardware is 8GB RAM, quad core CPU(5405), server 2003 64 bit, SQL 64 bit standart ed.

thanks

sinan