Hi all,

I got a scheduled task which will export sdo every 15 minutes using SDAPI. I
got following error in one of the export :

Description="Transaction (Process ID 68) was deadlocked on lock resources
with another process and has been chosen as the deadlock victim. Rerun the
transaction."

I want to ask what does it mean and would the content in this failure export
be exported in next export ?

Thanks so much

Tony

[ Post a follow-up to this message ]

Hi Tony,

first of all: running site deployment every 15 minutes is a very bad idea.
Site deployment import will lock the destination database for a short time
and request coming in during this time can cause 500 server errors and 404
page not found problems.

You should import only once a day and this should be done during times where
you expect less traffic.

Regarding the issue below: you need to analyze this on SQL server.
I assume that you have two import jobs running in parallel which is not
allowed.

Cheers,
Stefan

"Tony Cheng" <sdasd@fdfsds.com> wrote in message
news:etUox89fHHA.4692@TK2MSFTNGP03.phx.gbl...
> Hi all,
>
> I got a scheduled task which will export sdo every 15 minutes using SDAPI.
> I got following error in one of the export :
>
> Description="Transaction (Process ID 68) was deadlocked on lock resources
> with another process and has been chosen as the deadlock victim. Rerun the
> transaction."
>
> I want to ask what does it mean and would the content in this failure
> export be exported in next export ?
>
> Thanks so much
>
> Tony
>

[ Post a follow-up to this message ]

Hi Stefan,

Thanks for your reply. We have to run site deployment every 15 minutes
because the user want to deploy their postings to frontend within 20 minutes
after they approve the postings in backend.

Actually there is only one import job running.

Thanks

Tony




"Stefan Goßner [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23fs%23krAgHHA.1388@TK2MSFTNGP05.phx.gbl...
> Hi Tony,
>
> first of all: running site deployment every 15 minutes is a very bad idea.
> Site deployment import will lock the destination database for a short time
> and request coming in during this time can cause 500 server errors and 404
> page not found problems.
>
> You should import only once a day and this should be done during times
> where you expect less traffic.
>
> Regarding the issue below: you need to analyze this on SQL server.
> I assume that you have two import jobs running in parallel which is not
> allowed.
>
> Cheers,
> Stefan
>
> "Tony Cheng" <sdasd@fdfsds.com> wrote in message
> news:etUox89fHHA.4692@TK2MSFTNGP03.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Tony,

theny it is recommended to author against the production server.

Cheers,
Stefan


"Tony Cheng" <sdasd@fdfsds.com> wrote in message
news:uMk67VBgHHA.4260@TK2MSFTNGP03.phx.gbl...
> Hi Stefan,
>
> Thanks for your reply. We have to run site deployment every 15 minutes
> because the user want to deploy their postings to frontend within 20
> minutes after they approve the postings in backend.
>
> Actually there is only one import job running.
>
> Thanks
>
> Tony
>
>
>
>
> "Stefan Goßner [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:%23fs%23krAgHHA.1388@TK2MSFTNGP05.phx.gbl... 
>
>

[ Post a follow-up to this message ]