Hello!

We have a problem where a Hotfix exists (KB 816978) exists. But it is
recommanded to wait for the service pack.

Now my question: When will the next CMS Service Pack with this Hotfix will
be available?

Regards
--
Bernie

[ Post a follow-up to this message ]

Hi Bernie,

there is currently no schedule for a new service pack.
If you experience this problem install this hotfix.

The sentence about waiting for next SP is a standard disclaimer included in
nearly all hotfixes.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Bernie" <Bernd.no_spam.Hartlieb@atosorigin.com> wrote in message
news:9E0E5830-327F-4742-BA37-9908A0587AA5@microsoft.com...
> Hello!
>
> We have a problem where a Hotfix exists (KB 816978) exists. But it is
> recommanded to wait for the service pack.
>
> Now my question: When will the next CMS Service Pack with this Hotfix will
> be available?
>
> Regards
> --
> Bernie

[ Post a follow-up to this message ]

"Stefan [MSFT]" wrote:

> Hi Bernie,
>
> there is currently no schedule for a new service pack.
> If you experience this problem install this hotfix.
>
> The sentence about waiting for next SP is a standard disclaimer included i
n
> nearly all hotfixes.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...nagement+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "Bernie" <Bernd.no_spam.Hartlieb@atosorigin.com> wrote in message
> news:9E0E5830-327F-4742-BA37-9908A0587AA5@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Thanks Stefan,

please can you provide me an download link to get this hotfix (KB 816978)
for our customer ?

Hermann

"Stefan [MSFT]" wrote:

> Hi Bernie,
>
> there is currently no schedule for a new service pack.
> If you experience this problem install this hotfix.
>
> The sentence about waiting for next SP is a standard disclaimer included i
n
> nearly all hotfixes.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...nagement+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "Bernie" <Bernd.no_spam.Hartlieb@atosorigin.com> wrote in message
> news:9E0E5830-327F-4742-BA37-9908A0587AA5@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Herman,

I checked into the details of this bug and this hotfix is actually included
in CMS 2002 SP1 / SP1a.
So please install this already available service pack.

Cheers,
Stefan.


--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Hermann" <Hermann@discussions.microsoft.com> wrote in message
news:19CC24E7-D421-4B18-A5A5-C72F1449BA8A@microsoft.com...[vbcol=seagreen]
> Thanks Stefan,
>
> please can you provide me an download link to get this hotfix (KB 816978)
> for our customer ?
>
> Hermann
>
> "Stefan [MSFT]" wrote:
> 
in[vbcol=seagreen] 
rights.[vbcol=seagreen] 
http://download.microsoft.com/downl...
+Server[vbcol=seagreen] 
will[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hi Stefan,
we have CMS service pack 1a already installed - whats now ?
(it was already included on the setup cd).

But our hourly scheduled exports of the content fails very frequently with
error message:
"Error Export File D:\Deployment\Deployment.sdo since 0 : General network
error."
"Check your network documentation."

Within the last 5 days, 13 error occured:

Date              Time     Status
22.09.04        10:00    Export failed
22.09.04        07:00    Export failed
21.09.04        13:00    Export failed
21.09.04        11:00    Export failed
21.09.04        09:00    Export failed
20.09.04        17:00    Export failed
20.09.04        14:00    Export failed
20.09.04        11:00    Export failed
20.09.04        08:00    Export failed
19.09.04        17:00    Export failed
19.09.04        15:00    Export failed
18.09.04        16:00    Export failed
18.09.04        11:00    Export failed


"Stefan [MSFT]" wrote:

> Hi Herman,
>
> I checked into the details of this bug and this hotfix is actually include
d
> in CMS 2002 SP1 / SP1a.
> So please install this already available service pack.
>
> Cheers,
> Stefan.
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...nagement+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "Hermann" <Hermann@discussions.microsoft.com> wrote in message
> news:19CC24E7-D421-4B18-A5A5-C72F1449BA8A@microsoft.com... 
> in 
> rights. 
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm 
> http://www.gotdotnet.com/community/...nagement+Server 
> will 
>
>
>

[ Post a follow-up to this message ]

Hi Herman,

please test if the problem can be solved by configuring the protocol using
the SQL client tools to named-pipes rather than tcp.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Hermann" <Hermann@discussions.microsoft.com> wrote in message
news:9095A2ED-C30E-4B83-9DDA-CDACFA16EE47@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
> we have CMS service pack 1a already installed - whats now ?
> (it was already included on the setup cd).
>
> But our hourly scheduled exports of the content fails very frequently with
> error message:
> "Error Export File D:\Deployment\Deployment.sdo since 0 : General network
> error."
> "Check your network documentation."
>
> Within the last 5 days, 13 error occured:
>
> Date              Time     Status
> 22.09.04        10:00    Export failed
> 22.09.04        07:00    Export failed
> 21.09.04        13:00    Export failed
> 21.09.04        11:00    Export failed
> 21.09.04        09:00    Export failed
> 20.09.04        17:00    Export failed
> 20.09.04        14:00    Export failed
> 20.09.04        11:00    Export failed
> 20.09.04        08:00    Export failed
> 19.09.04        17:00    Export failed
> 19.09.04        15:00    Export failed
> 18.09.04        16:00    Export failed
> 18.09.04        11:00    Export failed
>
>
> "Stefan [MSFT]" wrote:
> 
included[vbcol=seagreen] 
rights.[vbcol=seagreen] 
http://download.microsoft.com/downl...
+Server[vbcol=seagreen] 
816978)[vbcol=seagreen] 
included[vbcol=seagreen] 
http://download.microsoft.com/downl...
+Server[vbcol=seagreen] 
is[vbcol=seagreen] 
Hotfix[vbcol=seagreen] 

[ Post a follow-up to this message ]