cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X

Translate the entire conversation x

mount failed for replica

gchampoux
7-Bedrock

mount failed for replica

I am installing and testing Windchill for the first time, specifically Intralink 9.1 M050.

Master server install and setup worked fine, as did the install for the replica server.
I defined the host, vault, and root for the replica (on the master).
However, when I attempt to mount the folder for the replica, I get this:

Create mount for root folder "ogreplicafolder" failed.
Nested exception is: wt.util.WTException: Mount status cannot be determined

After the first attempt, I thought that maybe the folder must already exist, so I created it and tried again.
Same error.
Found nothing about this in PTC's knowledgebase.
Any advice?

Gerry

16 REPLIES 16

Hi Gerry
Can you verify if the location you are mounting is writable or not. This can be checked by creating a new folder and a text file.
There are couple of other reasons also for this like if the Replica and Master are on same release including the Patches, the pubkey etc
Let me know if this doesnot help.
Thanks
Mayur

Yes, the location is writable.
As an extra test, I gave Everyone Full permissions to the folder.
Same error.

Hi Gerry, I'd bet that the Replica server isn't properly patched to the maintenance build that the master server is on. I've had issues similar to this and it was fixed by making sure it was good to go. I do know that replication works fine in the 9.1 M050 build as I just got finished with a full implementation of this to a Taiwan branch. If you can list out all the steps you did to install the replica that would help. Also go to the Replica server, open a Windchill shell and run "windchill version" and copy-paste the entire output here.

Steve Vinyard
Application Engineer

[cid:image001.gif@01CB2339.76663970]

Gerry --

Two questions:
(1) Is the folder location a mapped drive?
(2) Is Windchill running as a Service?

FYI -- If you're running Windchill on Windows as a Service, you cannot mount
a folder to a mapped drive. Services cannot write to mapped drives in
Windows. You will have to create a network share in order to mount the
folder. This is an easy thing to overlook.

On Tue, Jul 13, 2010 at 12:38 PM, Gerry Champoux

Hi Gerry, in my experience you HAVE to use the ServicePack that is downloaded from the master server. If I were you I would remove the existing replica install and start over using nothing but the files downloaded from the Master Server. I can almost guarantee this is what you are running into. I'm not sure about the ServicePack not showing any sort of "update" feature when you run it. You need to follow the guide on how to install the ccsDsu.zip file. I've attached the instructions on how to apply the Service Pack from the master server (CcsDsu.zip) file from the guide as well as the manual instructions for getting it to update as many times using the Auto-Update feature outlined in the guide fails. I just ran this operation on your exact build code with no issues so there are no bugs that I'm aware of (their used to be in M020).

Here is the outline:

1- Remove existing replica installation

2- Download all files from master site (see screenshot below)

3- Install Replica (no service pack installed)

4- Install ServicePack (CcsDsu.zip) - use the instruction set below (I'd just use the manual method at the bottom)

[cid:image001.png@01CB235E.FC014230]


Updating the File Server
Maintenance updates for a remote File Server are delivered by a zip file containing
all the necessary updates for a particular MOR. If "Enable Remote File Server
Support" was selected when installing the solution, this zip file is generated on the
master site when the maintenance updates are applied. It must then be downloaded
to the remote File Server so that it can be applied. The zip file should reside here
on the master site:

<windchill>/codebase/CCSTools/update/CcsDsu.zip


If Enable Remote File Server Support was not selected at the initial solution install,
this zip will not exist after applying the maintenance updates and will need to
be generated manually.

An Ant script which handles this task resides in
<windchill>/bin/CCSTools/create_ccsdsu.xml

This script creates the CcsDsu.zip based on a BOM (Bill Of Materials). It maintains a cumulative BOM, <wt_home>/codebase/CCSTools/CcsDsuBom.include, with which any future BOMs are merged.

To generate the zip, run the following command from a Windchill shell:
ant -f <windchill>/bin/CCSTools/create_ccsdsu.xml -Dinstall.files.maint=true <params>
where <params> are:
-Dccsdsubom_include (optional) = any alternative BOM file with contents relative
to <wt_home>.

This points to a BOM of contents to append to the CcsDsu.zip.

-Dccsdsu_exclude_list (optional) - A regular expression-based
list containing any files to exclude from the DSU (defaults to<wt_home>/installer/wnc/ccsdsu_regex_exclude_list.txt)
The script should run and generate the CcsDsu.zip and a corresponding MD5
checksum file in:
<windchill>/codebase/CCSTools/update

This DSU should then be downloaded to the remote File Server.

Ensure that the zip is placed in the same location as the master site:
<windchill>/codebase/CCSTools/update

The DSU will be applied when Windchill is restarted on the File Server.

Note
When applying an update (patch or Maintenance Release) to a master site that
has a cluster setup, the patch is applied to each of the nodes in the cluster
individually. However, for the CCS (File Server) automatic update to function
properly, the files in the <windchill>\CCSTools\update directory in the
master node(Background Method Server) of the cluster must be copied to the
<windchill>\CCSTools\update directory of each node in the cluster. This is
essential so that the CCSDsu.zip and its CCSDsu.zip.MD5 files on all nodes
are exactly the same.


How to Manually run the Upgrade:

Open a windchill shell
Navigate to <windchill_home>\bin\CCSTools\tools (wherever the install_ccsdsu.xml file)
set ANT_OPTS=-Xmx512m
ant -f install_ccsdsu.xml


Steve Vinyard
Application Engineer

[cid:image002.gif@01CB235E.FC014230]

All,
As a sanity check, take a look at the "site.xconf" file on the replication server. I have installed the replication server software three times in the last week and each time, the property "wt.intersvrcom.masterSite.1" was incorrect (causing similar, if not identical errors). For some reason, even though I supplied the correct name and path for the master server during the installation, a portion of the DNS name of the replication server was used for this property. The correct property setting should look something like this (your mileage may vary based on system configuration):

value="

First, thanks to everyone for trying to help me so far.
Although I still have the problem, we have identified (and fixed) one problem, and have more info.
I was using PTC's eLearning to do the install, which did not mention anything about the patch CcsDsu.zip.
I have completely reinitialized the test replica server, and reinstalled from scratch, including the patch.
Both the master and replica server now show the same Windchill version for all components: 9.1.50.10.

A couple of people suggested broadcasting the configuration. This too was not covered in the eLearning.
Broadcasting the configuration produced this message:

wt.wrmf.delivery.WTDeliveryException: (wt.wrmf.transport.httptransport.httptransportResource/2) wt.wrmf.transport.WTTransportException: Authentication to
"http://repsrvtest.williams-int.com/Windchill/servlet/WindchillGW" Failed.
Nested exception is: (wt.wrmf.transport.httptransport.httptransportResource/2) wt.wrmf.transport.WTTransportException: Authentication to "http://repsrvtest.williams-int.com/Windchill/servlet/WindchillGW" Failed.
Nested exception is: wt.wrmf.delivery.WTDeliveryException: (wt.wrmf.transport.httptransport.httptransportResource/2) wt.wrmf.transport.WTTransportException: Authentication to
"http://repsrvtest.williams-int.com/Windchill/servlet/WindchillGW" Failed.
Nested exception is: wt.wrmf.transport.WTTransportException: Authentication to
"http://repsrvtest.williams-int.com/Windchill/servlet/WindchillGW" Failed.

Where do I go from here?

Gerry

OK so it sounds like you are up to date now and on track with the guide. Definitely become very familiar with the guides as everything is in there. I would check that setting in some of the previous emails from another user. It could be a number of things with this, certainly log a PTC call as this is within their realm of expertise. Ask for a webex session. You might check all of the basic connectivities here. For replication to occur port 80 must be unblocked between the two. Try to ping one computer from the other and vise versa. Also make sure all Windows Firewall stuff is turned off, at least for testing.

The best route for getting help in these situations is recording each setting and step that you do in a document and then attaching it to the email so we can identify any small details that may have been missed. Eitherway, PTC should be able to find the mistake in there.



Steve Vinyard
Application Engineer

[cid:image001.gif@01CB236E.590BA060]

1) No.
2) No

No network shares are involved on either the master or replica server.

Gerry

More info:

Several people have asked me about pinging and firewall and ports.

All pings work fine (in both directions).

We have firewalls disabled on all servers and user PC's.
All firewall and related port blocking only apply to traffic going in/out to the Internet.

One exception: Our anti-virus does block programs that use port 25 (email) but I have that disabled the anti-virus on these test servers.

These test servers (master & replica) have only Windchill components installed.
So there should be no port conflicts with other applications.

Gerry

Hi Garry, go to the File Server Administrator>Site Management>Select the Replica Site>Click View and send out screenshots of the settings there. Also do this for your master site as well. Also attach your Site.xconf file also.

Since things are installed correctly now (assuming the automatic service pack update to replica was a success), go ahead and restart the method server for the master (leaving the replica method server up). After it has booted up, send out the series of related (latest) method servers.

This will allow us to see your settings and identify any errors there as well as see the method server log and any failures it's reporting as it tries to connect to replica when it starts up.

Steve Vinyard
Application Engineer

[cid:image001.gif@01CB2403.CEECAC30]
pwilliams-3
13-Aquamarine
(To:gchampoux)

Garry,
Did you by chance rename the the master site in the file vault
administrator? If you did then you will need to regenerate the replica
key that is used to configure the file server replica.

Patrick Williams
Sr. Systems Engineer II
Mechanical Engineering Solutions
Missile Systems
Raytheon Company

+1 520.545.6995 (business)
+1 520.545.6399 (fax)
-

TU/M12/8
6221 S Palo Verde Rd
Tucson, AZ 85706 USA
www.raytheon.com



This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.



The master site's name has been never chnaged throughout my tests.
However, I did regenerate the key to be sure.
Same folder mount error.

Jens,

Thank you for responding.

Some other people recommended the same action.
The xsite.conf property is correct, and we regenerated the security key
to be sure.
Didn't help.



Gerry

Gerry,

I think I have understood your issue as per the Logs you have pasted here.

As per the logs pasted here it says,
"wt.wrmf.transport.WTTransportException" error which means there is issue in
transport or communication between Master and Replica. There are many
reasons for this. I want you to try the following:-



A) The issue may be that your Pubkey is getting expired before it is being
used by Master and Replica to communicate to each other.



B) The other reason could be that your CcsDsu.zip is not getting
completely/fully installed on the Replica server .For a normal person it is
hard to know this b/c you need to check the Time and date stamp of few Class
files located in the Codebase.



C) I also see some unusual thing in your URL. Can you see if you Host (*
repsrvtest.williams-int.com*) is resolved by your domain. What I want to say
here is that try to see if you can really use the special characters "
repsrvtest.williams-int.com" for this.



So my suggestion would be to do the following, but keep in mind you do it on
a Test Server first and then see if this works (Normal scenario it should J)



*Solution for A:-*


1) Go to site.xconf and add the following property

<property name="wt.intersvrcom.security.graceTimePeriod" overridable="true"&lt;br"/>targetFile="codebase/wt.properties" value="1000000"/>

2) Save and propogate using xconfmanager -p.

3) Now do import and export of your Pubkey again and try to do broadcast
and let me know if you are able to do so.



If this fails please mail me the Log file at -



*Solution for B:-*



Try to re-apply the CcsDsu.zip. I need to understand are you doing it
manually or not.

Try to use the following commands:-

" ant ?f install_ccsdsu.xml -v" and mail me the output for this (
-).



*Solution for C:-*

Get in touch with PTC and ask them there is a Patch availabe for resolving
the Host /domain name and check if this is causing some issue. (I think this
should not be reoccurring b/c this was reported in 9.0 series and had been
fixed so not sure if this issue is coming again)

**



I really hope that above mentioned solutions will work for your problem. Let
me know in case it is solved or not.

**

Thanks

Mayur

**

**
On Thu, Jul 15, 2010 at 1:12 AM, Gerry Champoux
<->wrote:

> First, thanks to everyone for trying to help me so far.
> Although I still have the problem, we have identified (and fixed) one
> problem, and have more info.
> I was using PTC's eLearning to do the install, which did not mention
> anything about the patch CcsDsu.zip.
> I have completely reinitialized the test replica server, and reinstalled
> from scratch, including the patch.
> Both the master and replica server now show the same Windchill version for
> all components: 9.1.50.10.
>
> A couple of people suggested broadcasting the configuration. This too was
> not covered in the eLearning.
> Broadcasting the configuration produced this message:
>
> wt.wrmf.delivery.WTDeliveryException:
> (wt.wrmf.transport.httptransport.httptransportResource/2)
> wt.wrmf.transport.WTTransportException: Authentication to
> " Failed.
> Nested exception is:
> (wt.wrmf.transport.httptransport.httptransportResource/2)
> wt.wrmf.transport.WTTransportException: Authentication to "
> Failed.
> Nested exception is: wt.wrmf.delivery.WTDeliveryException:
> (wt.wrmf.transport.httptransport.httptransportResource/2)
> wt.wrmf.transport.WTTransportException: Authentication to
> " Failed.
> Nested exception is: wt.wrmf.transport.WTTransportException: Authentication
> to
> " Failed.
>
>
> Where do I go from here?
>
> Gerry
>
>
>

Success!

You guys are awesome.
After all the great advice, I was convinced that I must have mistyped a something during the installation or configuration of Windchill on the 2 servers.
Instead of trying to find those mistakes, I decided to start fresh.
I reinitialized both servers and reinstalled everything from scratch.

I can now broadcast the configuration without any error.
And the mount was successful.

Thank you all for your help.
Have a great weekend.
And inform your manager that you deserve a raise. <grin>

Gerry

Announcements
Top Tags