I've been running Exchange 2007 SP1 with the Edge role in my lab environment for sometime now and have not experienced
any problems. The lab consists of 2 servers: MSG-01 runs all Exchange 2007 roles while EDGE-01 runs the Edge-Gateway
role.

I attempted to renew the Edge subscription by creating a new XML file on the EDGE-01, copying the file to MSG-01 and
importing it. While attempting the import, I got the following error:

Error:
The version of the Edge subscription doesn't match any Hub Transport servers in the subscribed site.

I've verified the following:

- DNS resolution works. Each server can resolve the other.
- Time syc. Each server has its clock synchronized.
- I deleted the Edge subscription from MSG-01 before importing the new XML file. This didn't fix the problem.

What is causing this error?

Re: Edgesync fails subscription by Mohamed

Mohamed
Sun Mar 16 03:58:21 CDT 2008

how to remove edge subscribtion:
http://technet.microsoft.com/en-us/library/aa996865(EXCHG.80).aspx

If you did that right, restart both servers ( transport service by
Restart-Service MSExchangeTransport )



"Paul" <guardian911@gmail.com> wrote in message
news:tf6ot3lcktv3mm85hn03vfqmlup1o7cp24@4ax.com...
> I've been running Exchange 2007 SP1 with the Edge role in my lab
> environment for sometime now and have not experienced
> any problems. The lab consists of 2 servers: MSG-01 runs all Exchange 2007
> roles while EDGE-01 runs the Edge-Gateway
> role.
>
> I attempted to renew the Edge subscription by creating a new XML file on
> the EDGE-01, copying the file to MSG-01 and
> importing it. While attempting the import, I got the following error:
>
> Error:
> The version of the Edge subscription doesn't match any Hub Transport
> servers in the subscribed site.
>
> I've verified the following:
>
> - DNS resolution works. Each server can resolve the other.
> - Time syc. Each server has its clock synchronized.
> - I deleted the Edge subscription from MSG-01 before importing the new XML
> file. This didn't fix the problem.
>
> What is causing this error?
>