Posts by dnichols

I did similar, but I actually moved the entire software to another server, and regenerated the database there, and as long as the USB drive is local I can write to it...

Is anyone else using DICOM and writing images across network drives or Shares?

Can you explain what running a small subset locally would be? I'm not very fluent in DICOM systems...so If possible a few more details on steps needed to accomplish this would be greatly appreciated.

VVCIMAGE] UPACS THREAD 10: STARTED AT: Thu Jun 26 10:37:45 2014
[VVCIMAGE] Calling Application Title : "US_7 "
[VVCIMAGE] Called Application Title : "VVC_Image "
[VVCIMAGE] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16000
[VVCIMAGE] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.6.1" 1
[VVCIMAGE] [recompress]: recompressed with mode = un (strip=0)
[VVCIMAGE] ***Error writing file: U:\Dicom_Storage\78560\1.3.46.670589.14.3000.301.190155.3.20140626100540.1000000002_0001_000001_14037934650004.dcm
[VVCIMAGE] UPACS THREAD 10: ENDED AT: Thu Jun 26 10:37:45 2014
[VVCIMAGE] UPACS THREAD 10: TOTAL RUNNING TIME: 0 SECONDS

# This file contains configuration information for the DICOM server
# Do not edit unless you know what you are doing

[sscscp]
MicroPACS = sscscp
Edition = Personal

# Network configuration: server name and TCP/IP port#
MyACRNema = VVCIMAGE
TCPPort = 5678

# Reference to other files: known dicom servers; database layout; sops
ACRNemaMap = acrnema.map
kFactorFile = dicom.sql
SOPClassList = dgatesop.lst

# Host(ignored), name, username and password for ODBC data source
SQLHost = localhost
SQLServer = E:\DiCom_Storage\dicomserver\Data\dbase\conquest.db3
Username =
Password =
SqLite = 1
BrowseThroughDBF = 1
DoubleBackSlashToDB = 0
UseEscapeStringConstants = 0

# Configure database
TruncateFieldNames = 10
MaxFieldLength = 254
MaxFileNameLength = 255
FixPhilips = 0
FixKodak = 0
KeepAlive = 0
LargeFileSizeKB = 4096
PrintSquareLandscape = 0
UseKpacsDecompression = 1
ZipTime = 05:
UIDPrefix = 1.2.826.0.1.3680043.2.135.735133.61396011
EnableReadAheadThread = 1
PatientQuerySortOrder =
StudyQuerySortOrder =
SeriesQuerySortOrder =
ImageQuerySortOrder =
EnableComputedFields = 1
IndexDBF = 1
PackDBF = 0
LongQueryDBF = 1000
TCPIPTimeOut = 300
FailHoldOff = 60
RetryDelay = 100
RetryForwardFailed = 0
ImportExportDragAndDrop = 0
QueueSize = 128
WorkListMode = 0
WorkListReturnsISO_IR_100 = 1
DebugLevel = 0
Prefetcher = 0
LRUSort =
AllowTruncate =
DecompressNon16BitsJpeg = 1
UseBuiltInJPEG = 1
LossyQuality = 95
IgnoreOutOfMemoryErrors = 0
NoDICOMCheck = 0
PadAEWithZeros = 0
FileNameSyntax = 4

# Configuration of compression for incoming images and archival
DroppedFileCompression = un
IncomingCompression = un
ArchiveCompression = as

# Names of the database tables
PatientTableName = DICOMPatients
StudyTableName = DICOMStudies
SeriesTableName = DICOMSeries
ImageTableName = DICOMImages
DMarkTableName = DICOMAccessUpdates
RegisteredMOPDeviceTable = RegisteredMOPIDs
UIDToMOPIDTable = UIDToMOPID
UIDToCDRIDTable = UIDToCDRID

# Banner and host for debug information
PACSName = VVCIMAGE
OperatorConsole = 127.0.0.1

# Configure email of error messages
MailHost =
MailPort = smtp
MailSignon =
MailFromName =
MailRcptName1 =
MailCollectTime = 1
MailWaitTime = 10

# Configuration of disk(s) to store images
MAGDeviceThreshhold = 0
MAGDeviceFullThreshHold = 30
IgnoreMAGDeviceThreshold = 0
MAGDevices = 1
MAGDevice0 = U:\Dicom_Storage\
NightlyCleanThreshhold = 0

I'm not quite sure how to set that check to 0?
Total size of the IMAGE directory is ~900 Gigs, but any one file is not larger than a few megs each.

As far as the write error goes, I can't seem to write images across network mapped drives.

If I plug in a local USB, or save to a local Volume Images will save.

But the moment I try to set the Dicom Storage to our NAS ( or in this case a shared drive on another server) I get this write error.

I've opened up ALL Permissions NTFS and shared...but still nothing.

I'm having trouble with a database I'm trying to reinitialize.

sqllite installation. Newest version of software:

[VVCIMAGE] [Regen] U:\Dicom_Storage\000647\1.2.840.113543.6.6.4.0.63956770443185455852011376271563381140874_0001_000012_139404664386a9.dcm -SUCCESS
[VVCIMAGE] ***VR:ReAlloc out of memory allocating 574560000 bytes
[VVCIMAGE] ***A fatal error occurred (out of memory) - closing server
------------------- Finished database regeneration --------------------

Also, when machine try to write to database:

[VVCIMAGE] [recompress]: recompressed with mode = un (strip=0)
[VVCIMAGE] ***Error writing file: U:\Dicom_Storage\59820\1.2.840.113619.2.115.11481584.1403700670.0.1690_0003_000001_1403727937009e.dcm
[VVCIMAGE] UPACS THREAD 164: ENDED AT: Wed Jun 25 16:25:37 2014
[VVCIMAGE] UPACS THREAD 164: TOTAL RUNNING TIME: 3 SECONDS

I have a Drive shared across a network to store the DICOM Images on another server:
Basic Sharing, EVERYONE allowed to read/write.

Any ideas?

Windows Server 2003, updated with recent service packs and security updates.
DGATE get an application error and will no longer accept connections.
Fix is to restart Service and IISReset to allow website query to run again.

DGate 1.4.16k, Build Sun Jul 01, 2012 32 bit

Multiple crashes over several days see below: If I reboot server I get about a week of stability before the daily crashes begin again.
This is the only application that has trouble on the system.

Faulting application dgate.exe, version 0.0.0.0, faulting module dgate.exe, version 0.0.0.0, fault address 0x0004fff4.
Faulting application dgate.exe, version 0.0.0.0, faulting module dgate.exe, version 0.0.0.0, fault address 0x00050294.
Faulting application dgate.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x0730c3ed.

Any help would be appreciated.