Skip to main content
July 13, 2010
Question

mount failed for replica

  • July 13, 2010
  • 16 replies
  • 3502 views

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

1-Visitor
July 15, 2010
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]
13-Aquamarine
July 15, 2010
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.



July 15, 2010

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.

July 15, 2010
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

1-Visitor
July 15, 2010
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
>
>
>
July 16, 2010

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