Is there a log file created with a more explicit error message description beyond the error message code ? Please share.
The Replicate documentation seems to be behind the times in its "Disk requirements" using decades old lingo like 'rpm' and does not mention SSD or similar. The whole section is labeled "Recommended hardware configuration". One could interpret that as 'not required' and there is no explicit mention of network attached storage (NAS).
The Replicate DATA disk access can be the defining factor in Replicate performance. This is notably the case when long running transactions which may have to be staged in workfiles; when the target is slow requiring further staging; when multiple GB transaction sorting is needed; when (multiple GB) CSV files are to be produced.
As such Replicate does not want to get a bad name caused by poor storage choices and may well require a 'real' disk or a device not distinguishable from that during installation. I suppose it should document that clearly and give a clear non-compliance message if/when it does an active test, but here we are.
I would strongly recommend NOT bothering with an NFS style data drive for the above reasons.
If you want to try that anyway then I'd suggest to go ahead and install using a 'local' disk first, even if that were to be the 'c:' drive for now. Once you have a successful installation you can start 'playing' with it. For that follow the documented instructions under "Changing the Data Directory location on Windows". Using this approach you will at least know what worked, what broke, and you'll have (hopefully) clear information in a 'repsrv.log' if it fails. ( Hmmm, actually, there is probably no regular repsrv.log or at best it is in the bin directory, as it normally would be located on that data drive :-). Check the windows event logs ?!
hth,
Hein.
