ATTACHING VOLUMES FROM ONE LOC TO ANOTHER ON WAN (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== ATTACHING VOLUMES FROM ONE LOC TO ANOTHER ON WAN (AREV Specific) ====
=== At 15 JUN 1998 05:38:26PM Brian M. wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
  We have just upgraded arev from 2.12 to 3.12 and migrated our platform to NT servers and NT workstations.  NT service is installed and running. On one location of our WAN we are trying to attach (setalias) to another location. We can map to the location and see/edit all the DOS/TEXT files in the directories but cannot attach the REV files.  We have tried setalias, setting up volumes to the location, and attaching at TCL.  The error msgs we get range from:

 'the "X" table at the "y" location is not available or does not exist'

  'unable to attach the "y" location'

 ' open or create media error' the name is an invalid volume directory'

 'Maximum number of Advanced Revelation users exceeded'

We have used these types of setalias commands for many years and in fact these volume labels were working just the day before. Th only change that we are aware of is that more users have logged in at the other location.  Any insight you can offer for these problems will be appreciated
</QUOTE>
----

=== At 18 JUN 1998 10:08PM Kevin at KPW wrote:  ===

<QUOTE>Brian,



When you map to the remote server one assumes you are using

something like this .....



Map say K: to //ntserver1/apps/  



Where ntserver1 is the remote server.



Within the apps directory you may have your AREV directory set up

as say AREVDIR



Within that you may have your application data directory e.g. DATA1



Then within AREV you would be attaching at AREV logon thus ....



ATTACHTABLE K:\AREVDIR\DATA1



to attach all tables within that location. Alternatively you would only

attach the particular tables required e.g. 



ATTACHTABLE K:\AREVDIR\DATA1 table1 table2 etc



Are you saying that this will not work?



Do you have separate NT Service Licenses on each server?



Are you using the REVPARAM within each data directory at each

location?



Regards,

Kevin at KPW

Adelaide - South Australia

email kpw1@compuserve.com

</QUOTE>

----

=== At 27 JUN 1998 12:05PM Aaron Kaplan wrote:  ===

<QUOTE>By migrated, I assume you mean you were using Novell before?  Just out of curiosity, did you do both moves at once or did you phase them in?



Are you setting the map before entering ARev or after?  Sometimes ARev does not like network drives that are mapped after ARev has been loaded.  You say you can see the files with DOS commands.  Is this from another DOS box or did you do a PC or SUSPEND?



If you have ServerOnly=1 set (which you should) it could be that you are not seeing the service across the WAN.



On the other hand, if you are using the same copy of the service on both servers, they won't talk to each other.





akaplan@sprezzatura.com

[url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url]

[img]http://www.sprezzatura.com/zz.jpg[/img]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=F59D0563D9B94F08852566240076E013|View this thread on the  forum...]]