Connection to the Version Manager Could Not Be Established

Because of NOF 10 crashing some of my sites, I've decided to stop using NOF 
10 and I'm recreating the sites in NOF 9 for now.

In the Current Site Options, under Versioning, I've selected the Publish 
Profile and entered the Repository path, just like I did in NOF 10.  When I 
do this, I get the errors "Unable to Connect to Publish Manager" and
"Unable 
to Connect to Versioning Manager."  I don't understand the reason for the 
first error message because I don't have any problems publishing the site 
using that Publish Profile.

If I try to open the Version Manager, I get the following message:

"A connection to the Version Manager could not be established.  A
connection 
to the Version Manager must be established to check for the latest version 
of this site and to access other important features."

I had the "repository path" password protected using my webhosts
Cpanel 
features, just to keep everyone else from accessing the version files--that 
was not a problem in NOF 10.  I went in and unprotected that folder and it 
did not make any difference.

Any thoughts on why I'm getting this error in NOF 9?

Thanks,

Brian 

bw schreef:
> Because of NOF 10 crashing some of my sites, I've decided to stop using NOF

> 10 and I'm recreating the sites in NOF 9 for now.
> 
> In the Current Site Options, under Versioning, I've selected the Publish 
> Profile and entered the Repository path, just like I did in NOF 10.  When I

> do this, I get the errors "Unable to Connect to Publish Manager"
and "Unable 
> to Connect to Versioning Manager."  I don't understand the reason for
the 
> first error message because I don't have any problems publishing the site 
> using that Publish Profile.
> 
> If I try to open the Version Manager, I get the following message:
> 
> "A connection to the Version Manager could not be established.  A
connection 
> to the Version Manager must be established to check for the latest version

> of this site and to access other important features."
> 
> I had the "repository path" password protected using my webhosts
Cpanel 
> features, just to keep everyone else from accessing the version files--that

> was not a problem in NOF 10.  I went in and unprotected that folder and it

> did not make any difference.
> 
> Any thoughts on why I'm getting this error in NOF 9?
> 
> Thanks,
> 
> Brian 
> 
> 

Jos Roijakkers schreef:
> bw schreef:
>> Because of NOF 10 crashing some of my sites, I've decided to stop 
>> using NOF 10 and I'm recreating the sites in NOF 9 for now.
>>
>> In the Current Site Options, under Versioning, I've selected the 
>> Publish Profile and entered the Repository path, just like I did in 
>> NOF 10.  When I do this, I get the errors "Unable to Connect to 
>> Publish Manager" and "Unable to Connect to Versioning
Manager."  I 
>> don't understand the reason for the first error message because I 
>> don't have any problems publishing the site using that Publish
Profile.
>>
>> If I try to open the Version Manager, I get the following message:
>>
>> "A connection to the Version Manager could not be established.  A

>> connection to the Version Manager must be established to check for the

>> latest version of this site and to access other important
features."
>>
>> I had the "repository path" password protected using my
webhosts 
>> Cpanel features, just to keep everyone else from accessing the version

>> files--that was not a problem in NOF 10.  I went in and unprotected 
>> that folder and it did not make any difference.
>>
>> Any thoughts on why I'm getting this error in NOF 9?
>>
>> Thanks,
>>
>> Brian
>>
> I have exactly same problem (using NOF9).
It seems that the latest version of NOF9 (9.1 build 5035) assumes a 
subfolder named "_versioning_repository_" is present. So if you use
the 
repository path "/MyFolder/" you manually (!) have to create a folder

"/MyFolder/_versioning_repository_". Take notice of the underscores in

this name.
IIRC, with older NOF versions this subfolder was created automatically 
if it did not exist.

Jos,

Thanks for the help.

I looked at NOF help and didn't see anything about having to have the 
version path to be named _versioning_repository_ .  However I did that and I 
also created a folder by that name.  So now when I click OK for the Options 
| Current Site, I don't get error messages at that point anymore.

But when I try to open the Versions Manager, I'm still getting the 
Connection to the Version Manager Could Not Be Established error.

I chose the same Publish Profile that I've been using without any problems 
so I'm not sure what the problem is now.

Brian


"Jos Roijakkers" <jos@jr-video.nl> wrote in message 
news:fr0evd$klk3@flsun90netnews01.netobjects.com...
> Jos Roijakkers schreef:
>> bw schreef:
>>> Because of NOF 10 crashing some of my sites, I've decided to stop
using 
>>> NOF 10 and I'm recreating the sites in NOF 9 for now.
>>>
>>> In the Current Site Options, under Versioning, I've selected the
Publish 
>>> Profile and entered the Repository path, just like I did in NOF 10.

>>> When I do this, I get the errors "Unable to Connect to Publish
Manager" 
>>> and "Unable to Connect to Versioning Manager."  I don't
understand the 
>>> reason for the first error message because I don't have any
problems 
>>> publishing the site using that Publish Profile.
>>>
>>> If I try to open the Version Manager, I get the following message:
>>>
>>> "A connection to the Version Manager could not be established.
 A 
>>> connection to the Version Manager must be established to check for
the 
>>> latest version of this site and to access other important
features."
>>>
>>> I had the "repository path" password protected using my
webhosts Cpanel 
>>> features, just to keep everyone else from accessing the version 
>>> files--that was not a problem in NOF 10.  I went in and unprotected
that 
>>> folder and it did not make any difference.
>>>
>>> Any thoughts on why I'm getting this error in NOF 9?
>>>
>>> Thanks,
>>>
>>> Brian
>>>
>> I have exactly same problem (using NOF9).
> It seems that the latest version of NOF9 (9.1 build 5035) assumes a 
> subfolder named "_versioning_repository_" is present. So if you
use the 
> repository path "/MyFolder/" you manually (!) have to create a
folder 
> "/MyFolder/_versioning_repository_". Take notice of the
underscores in 
> this name.
> IIRC, with older NOF versions this subfolder was created automatically if 
> it did not exist.
> Anyway, my problem is solved. 

This is what we did for V9 - It may help you a bit.

http://www.1ahost.co.uk/html/nof9_version_manager.html

-- 
Ian
1AHost

Free Web Hosting - PHP & MySQL Hosting
Resellers and Affiliates Schemes
www.1ahost.co.uk


"bw" <bw@nospam.com> wrote in message 
news:fr1kpq$paj1@flsun90netnews01.netobjects.com...
> Jos,
>
> Thanks for the help.
>
> I looked at NOF help and didn't see anything about having to have the 
> version path to be named _versioning_repository_ .  However I did that and

> I also created a folder by that name.  So now when I click OK for the 
> Options | Current Site, I don't get error messages at that point anymore.
>
> But when I try to open the Versions Manager, I'm still getting the 
> Connection to the Version Manager Could Not Be Established error.
>
> I chose the same Publish Profile that I've been using without any problems

> so I'm not sure what the problem is now.
>
> Brian
>
>
> "Jos Roijakkers" <jos@jr-video.nl> wrote in message 
> news:fr0evd$klk3@flsun90netnews01.netobjects.com...
>> Jos Roijakkers schreef:
>>> bw schreef:
>>>> Because of NOF 10 crashing some of my sites, I've decided to
stop using 
>>>> NOF 10 and I'm recreating the sites in NOF 9 for now.
>>>>
>>>> In the Current Site Options, under Versioning, I've selected
the 
>>>> Publish Profile and entered the Repository path, just like I
did in NOF 
>>>> 10. When I do this, I get the errors "Unable to Connect to
Publish 
>>>> Manager" and "Unable to Connect to Versioning
Manager."  I don't 
>>>> understand the reason for the first error message because I
don't have 
>>>> any problems publishing the site using that Publish Profile.
>>>>
>>>> If I try to open the Version Manager, I get the following
message:
>>>>
>>>> "A connection to the Version Manager could not be
established.  A 
>>>> connection to the Version Manager must be established to check
for the 
>>>> latest version of this site and to access other important
features."
>>>>
>>>> I had the "repository path" password protected using
my webhosts Cpanel 
>>>> features, just to keep everyone else from accessing the version

>>>> files--that was not a problem in NOF 10.  I went in and
unprotected 
>>>> that folder and it did not make any difference.
>>>>
>>>> Any thoughts on why I'm getting this error in NOF 9?
>>>>
>>>> Thanks,
>>>>
>>>> Brian
>>>>
>>> I have exactly same problem (using NOF9).
>> It seems that the latest version of NOF9 (9.1 build 5035) assumes a 
>> subfolder named "_versioning_repository_" is present. So if
you use the 
>> repository path "/MyFolder/" you manually (!) have to create
a folder 
>> "/MyFolder/_versioning_repository_". Take notice of the
underscores in 
>> this name.
>> IIRC, with older NOF versions this subfolder was created automatically
if 
>> it did not exist.
>> Anyway, my problem is solved.
>
>