|
Home > Archive > Microsoft Content Management Server > August 2005 > Locking Owner
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Let me explain the environment.
We have three environments that we migrate the MCMS database too. Dev, QA,
then finally a production instance. These are all different physical W2K3 web
servers and MSSQL 2000 database servers on W2K.
We create, edit, and publish the content in our development environment.
Once it’s all published, we use the Site Manager tool to do an export of that
content. We then use the Site Manager in the next environment to import that
SDO file into the QA. We eventually do the same to production once we know
all issues have been worked out of the SDO.
On of the problems that we can’t seem to find a good work around for is if
(for some unknown reason) a UserID has the content marked with his ID instead
of EVERYONE for the locking owner. The content can not be displayed.
What I have found, I am using my ID, which is different from the person with
the locking owner flag, but I am in the Administrators group within MCMS. If
I do an import. It looks like it updates the content, but will not change the
locking owner flag. The only way we have been able to work around the issue,
is if the person, who has the locking owner flag does the SDO import. It’ll
revert the locking owner to EVERYONE. Until EVERYONE is marked as the locking
owner, no one can view the page as we are using generic authentication.
The only other way we have found is the remove and recreate the content from
scratch.
One other thing to consider, we do a series of SDO files, incremental, but
eventually the next version contains all of the previos, plus new content to
the QA, until QA has all the content and bugs are fixed. Then this last SDO
import version is the only one applied to production.
What bothers us the most, when the export of the last SDO version was done.
We know for a fact that the locking owner was correct, but when we import
this file into the production MCMS database, that locking owner will show up
again.
Initially, we thought that one of the prevous imported SDO files contained
the issue and all successive SDO’s after that just could not update the
locking owner, but that does not seem to be the case. It looks like it’ll
bring a revision history with the SDO imports and apply the changes in order.
So somewhere in the SDO, there is a play where the locking owner information
is stored. We have unzipped the SDO and have taken a look at it, but I just
can’t find where it’s keeping this information.
Any idea’s?
Thanks
Dave
| |
| Stefan [MSFT] 2005-08-03, 5:52 pm |
| Hi Dave,
what if you open VS.NET and check-in the template on the machine where it
has been checked out?
This will work if you are an administrator.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:8A357A64-3D57-4FD6-B1AD-4CF29413CD8F@microsoft.com...
> Let me explain the environment.
>
> We have three environments that we migrate the MCMS database too. Dev, QA,
> then finally a production instance. These are all different physical W2K3
> web
> servers and MSSQL 2000 database servers on W2K.
>
> We create, edit, and publish the content in our development environment.
> Once it's all published, we use the Site Manager tool to do an export of
> that
> content. We then use the Site Manager in the next environment to import
> that
> SDO file into the QA. We eventually do the same to production once we know
> all issues have been worked out of the SDO.
>
> On of the problems that we can't seem to find a good work around for is if
> (for some unknown reason) a UserID has the content marked with his ID
> instead
> of EVERYONE for the locking owner. The content can not be displayed.
>
> What I have found, I am using my ID, which is different from the person
> with
> the locking owner flag, but I am in the Administrators group within MCMS.
> If
> I do an import. It looks like it updates the content, but will not change
> the
> locking owner flag. The only way we have been able to work around the
> issue,
> is if the person, who has the locking owner flag does the SDO import. It'll
> revert the locking owner to EVERYONE. Until EVERYONE is marked as the
> locking
> owner, no one can view the page as we are using generic authentication.
>
> The only other way we have found is the remove and recreate the content
> from
> scratch.
>
> One other thing to consider, we do a series of SDO files, incremental, but
> eventually the next version contains all of the previos, plus new content
> to
> the QA, until QA has all the content and bugs are fixed. Then this last
> SDO
> import version is the only one applied to production.
>
> What bothers us the most, when the export of the last SDO version was
> done.
> We know for a fact that the locking owner was correct, but when we import
> this file into the production MCMS database, that locking owner will show
> up
> again.
>
> Initially, we thought that one of the prevous imported SDO files contained
> the issue and all successive SDO's after that just could not update the
> locking owner, but that does not seem to be the case. It looks like it'll
> bring a revision history with the SDO imports and apply the changes in
> order.
> So somewhere in the SDO, there is a play where the locking owner
> information
> is stored. We have unzipped the SDO and have taken a look at it, but I
> just
> can't find where it's keeping this information.
>
> Any idea's?
>
> Thanks
> Dave
>
| |
|
| That is the weird part. The content is not locked. It just has a Locking
Owner as a user id. If I click on the content and try to remove locks, they
don't exist. I've tried that on the whole thread, and no locks exist.
So it's not a lock that is an issue, it simple a "locking owner".
Thanks
Dave
"Stefan [MSFT]" wrote:
> Hi Dave,
>
> what if you open VS.NET and check-in the template on the machine where it
> has been checked out?
> This will work if you are an administrator.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:8A357A64-3D57-4FD6-B1AD-4CF29413CD8F@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2005-08-03, 5:52 pm |
| Hi Dave,
then checkout and checkin the item again.
Does this remove the lock?
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:DC95785D-FF8C-43AA-A5B1-DE9B73449224@microsoft.com...[vbcol=seagreen]
> That is the weird part. The content is not locked. It just has a Locking
> Owner as a user id. If I click on the content and try to remove locks,
> they
> don't exist. I've tried that on the whole thread, and no locks exist.
>
> So it's not a lock that is an issue, it simple a "locking owner".
> Thanks
> Dave
>
> "Stefan [MSFT]" wrote:
>
| |
|
| Yes, we've tried modifying the content on the dev system again, checking it
back in and approve it. Then we export it and move it to QA. The QA system
won't change the locking owner.
We have to remove the content or let the locking owner do the import. Both
of those solutions fix the issue, but this will be a nightware when we have
10-20-30 locking owners for content authors.
We have even tried to create the locking owner issue and can't figure out
how to manually create it. It's happening on some content once in a while.
1600 pages updated last time and 19 pages with this issue.
Thanks
Dave
"Stefan [MSFT]" wrote:
> Hi Dave,
>
> then checkout and checkin the item again.
> Does this remove the lock?
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:DC95785D-FF8C-43AA-A5B1-DE9B73449224@microsoft.com...
>
>
>
| |
|
| To clarify one more thing. The locking owner updates fine on the dev system
where they do the edits. It's the QA/Prod boxes that won't update with the
imports.
We've tried exporting user rights/roles also and that has not solved the
issue, deleted or not deleted the content with the import. Nothing has worked
to change the locking owner except remove and recreate or having the owner do
the import.
Dave
"Stefan [MSFT]" wrote:
> Hi Dave,
>
> then checkout and checkin the item again.
> Does this remove the lock?
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:DC95785D-FF8C-43AA-A5B1-DE9B73449224@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2005-08-03, 5:52 pm |
| Hi Dave,
you need to do this on the QA system!
The item got logged out on the QA system - it cannot be logged in from a
different system.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:E9A34200-0C34-4E8D-BE36-3994872E3C97@microsoft.com...[vbcol=seagreen]
> Yes, we've tried modifying the content on the dev system again, checking
> it
> back in and approve it. Then we export it and move it to QA. The QA system
> won't change the locking owner.
>
> We have to remove the content or let the locking owner do the import. Both
> of those solutions fix the issue, but this will be a nightware when we
> have
> 10-20-30 locking owners for content authors.
>
> We have even tried to create the locking owner issue and can't figure out
> how to manually create it. It's happening on some content once in a while.
> 1600 pages updated last time and 19 pages with this issue.
>
> Thanks
> Dave
>
> "Stefan [MSFT]" wrote:
>
| |
|
| OK..We figured this was the only way to fix that issue. But somehow, this
status was imported this way. It it supposed to allow content to import if it
has not been published/accepted?
Is there a way to script and export so it will not do that? or a flag
somewhere that I can set?
Thanks
Dave
"Stefan [MSFT]" wrote:
> Hi Dave,
>
> you need to do this on the QA system!
> The item got logged out on the QA system - it cannot be logged in from a
> different system.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:E9A34200-0C34-4E8D-BE36-3994872E3C97@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2005-08-04, 2:47 am |
| Hi Dave,
if everything goes rights an item cannot be exported when it is locked - so
there should be no way to import such an item.
If it still happens then this would indicate a database inconsistancy either
on your source or on your destination system.
The only way to get a database inconsistancy fixed is to open a support case
with Microsoft.
Be aware that this only makes sense if you have a SDO file that generates
such a problem.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:43AEF697-935F-497C-86F1-3709344341B3@microsoft.com...[vbcol=seagreen]
> OK..We figured this was the only way to fix that issue. But somehow, this
> status was imported this way. It it supposed to allow content to import if
> it
> has not been published/accepted?
>
> Is there a way to script and export so it will not do that? or a flag
> somewhere that I can set?
>
> Thanks
> Dave
>
> "Stefan [MSFT]" wrote:
>
| |
|
| We were thinking the same end result. I do want to clear one thing up. It's
not a template issue. It's a content issue that this is on. It's not locking
but Locking Owner. Somehow this is set to a UserID on import instead of
Everyone.
Thanks for some insight.
Dave
"Stefan [MSFT]" wrote:
> Hi Dave,
>
> if everything goes rights an item cannot be exported when it is locked - so
> there should be no way to import such an item.
> If it still happens then this would indicate a database inconsistancy either
> on your source or on your destination system.
>
> The only way to get a database inconsistancy fixed is to open a support case
> with Microsoft.
>
> Be aware that this only makes sense if you have a SDO file that generates
> such a problem.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:43AEF697-935F-497C-86F1-3709344341B3@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2005-08-05, 5:52 pm |
| Hi Dave,
this question cannot be answered without a repro with your source and
destination databases and SDO file.
You need to open a support case to check if this problem is caused by a
database inconsistancy.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:62030B44-4513-490F-8463-9F840A9C2F78@microsoft.com...[vbcol=seagreen]
> We were thinking the same end result. I do want to clear one thing up.
> It's
> not a template issue. It's a content issue that this is on. It's not
> locking
> but Locking Owner. Somehow this is set to a UserID on import instead of
> Everyone.
>
> Thanks for some insight.
>
> Dave
>
> "Stefan [MSFT]" wrote:
>
| |
|
| Will do.
Thanks for your help.
"Stefan [MSFT]" wrote:
[vbcol=seagreen]
> Hi Dave,
>
> this question cannot be answered without a repro with your source and
> destination databases and SDO file.
> You need to open a support case to check if this problem is caused by a
> database inconsistancy.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:62030B44-4513-490F-8463-9F840A9C2F78@microsoft.com...
|
|
|
|
|