Schema Not Compatible Error
Apr 21, 2010
11:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Apr 21, 2010
11:28 AM
Schema Not Compatible Error
Hi All,
Updated Intralink 3.4 from M040 to M062 over the weekend everything has
worked fine until about an hour ago. Started receiving the following
error.
Any suggestions???
Regards,
Mark
WEBER AIRCRAFT LLC
SEATS
Mark Swarner
ENGINEER II
2000 Weber Drive - Gainesville - TX - 76240
Tel: (940) 668-4100 x4449
Mark.Swarner@zodiacaerospace.com
Updated Intralink 3.4 from M040 to M062 over the weekend everything has
worked fine until about an hour ago. Started receiving the following
error.
Any suggestions???
Regards,
Mark
WEBER AIRCRAFT LLC
SEATS
Mark Swarner
ENGINEER II
2000 Weber Drive - Gainesville - TX - 76240
Tel: (940) 668-4100 x4449
Mark.Swarner@zodiacaerospace.com
2 REPLIES 2
Apr 23, 2010
08:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Apr 23, 2010
08:49 AM
Mark,
Did you remove your M040 client? If you were using an M062, closed it, and
then opened the old M040 client, that would explain why it worked for awhile
then stopped working. The client, dataserver, and fileserver have to be the
same build code (M062).
Best Regards,
Bill Palm
Director - RAPiDS Support Center
ProductSpace Solutions, Inc.
Office: 630.495.2999 X8102
Cell: 630.460.4903
On Wed, Apr 21, 2010 at 10:28 AM, Mark Swarner <
mark.swarner@zodiacaerospace.com> wrote:
> Hi All,
>
> Updated Intralink 3.4 from M040 to M062 over the weekend everything has
> worked fine until about an hour ago. Started receiving the following error.
>
>
>
>
> Any suggestions???
>
> Regards,
> Mark
> *WEBER AIRCRAFT LLC*
> SEATS [image: logo] *Mark Swarner*
> ENGINEER II 2000 Weber Drive - Gainesville - TX - 76240
> Tel: (940) 668-4100 x4449
> Mark.Swarner@zodiacaerospace.com
>
Did you remove your M040 client? If you were using an M062, closed it, and
then opened the old M040 client, that would explain why it worked for awhile
then stopped working. The client, dataserver, and fileserver have to be the
same build code (M062).
Best Regards,
Bill Palm
Director - RAPiDS Support Center
ProductSpace Solutions, Inc.
Office: 630.495.2999 X8102
Cell: 630.460.4903
On Wed, Apr 21, 2010 at 10:28 AM, Mark Swarner <
mark.swarner@zodiacaerospace.com> wrote:
> Hi All,
>
> Updated Intralink 3.4 from M040 to M062 over the weekend everything has
> worked fine until about an hour ago. Started receiving the following error.
>
>
>
>
> Any suggestions???
>
> Regards,
> Mark
> *WEBER AIRCRAFT LLC*
> SEATS [image: logo] *Mark Swarner*
> ENGINEER II 2000 Weber Drive - Gainesville - TX - 76240
> Tel: (940) 668-4100 x4449
> Mark.Swarner@zodiacaerospace.com
>
Apr 23, 2010
08:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Apr 23, 2010
08:58 AM
Thanks for the reply, Bill.
I looked into that, even launch Ilink directly from the M062 "bin"
directory and still got the same result. Funny thing (or maybe not) is
that about 20 minutes later the problem went away. I am in the process of
un-installing M040 from the clients just in case that is causing the
issue.
Regards,
Mark
WEBER AIRCRAFT LLC
SEATS
Mark Swarner
ENGINEER II
2000 Weber Drive - Gainesville - TX - 76240
I looked into that, even launch Ilink directly from the M062 "bin"
directory and still got the same result. Funny thing (or maybe not) is
that about 20 minutes later the problem went away. I am in the process of
un-installing M040 from the clients just in case that is causing the
issue.
Regards,
Mark
WEBER AIRCRAFT LLC
SEATS
Mark Swarner
ENGINEER II
2000 Weber Drive - Gainesville - TX - 76240
