Do you have a question?

First Name:
Surname:
Email:
Phone:
Message:
Get Audio Code

ImageServerAlpha Replication on MS SQL 2008 R2 64-Bits
Last Post 09 Jul 2013 08:56 AM by Clinton C. 2 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Ali JUser is Offline
New Member
New Member
Posts:14

--
19 Jun 2013 07:43 PM  

We have ImageServerAlpha DB running on MS SQL 2008 R2 64-Bits Server.  We would like to replicate the DB from production site to remote site.  First I created Publication using "Transactional Publication" & selected "Tables", "Stored Procedures" & "User Defined Functions".  Then I created Subscriptions.  After the Snapshot & replication jobs completed, All the "Server Partition", "Devices" & "Logs" & etc replicated fine.  But when I select Studies on broweser & select any Server Partition & search for the studies with or without any critaria, I got the error below on the remote server

Error: "Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.
Details: Error parsing near '

 

Then I deleted the Publication & Subscription & re-created to replicate All Tables Only.  But got the same result.
Do I have to replicate any specific tables?
I am using DFS to copy the images, *.dcm files.
Can you please help me accomplish this task, I would really appreciate it?
Thank You in Advance

Ali JUser is Offline
New Member
New Member
Posts:14

--
08 Jul 2013 03:03 PM  

Stewart and resnickj

Can you please help?  I would really apprecite it.

Thanks...

Clinton CUser is Offline
Basic Member
Basic Member
Posts:129

--
09 Jul 2013 08:56 AM  

Dear ajafri10:

Thank you for posting your inquiry on our forums. 

I would like to offer a word of caution to you, however, on your use of the ImageServer Alpha version. 

The Alpha version was intended to be a "preview" of later, commercial products and not intended to be deployed in a production environment, as it seems you are now doing. Not only that, the Community Edition products are meant as reference, education and research tools, not to be used in clinical settings, as the Community Edition products are not included in our FDA clearance.

Thus, to use the Community Edition products in a clinical setting greatly exposes you to medicolegal liability.

Please exercise proper discretion in the appropriate use of these software applications. 

Thank you,

Clinton

 

You are not authorized to post a reply.

Active Forums 4.1