G
Guest
Hello,
we are experiencing severe problems within a rollout of an
asp.net-application. The symptoms are very similay to the ones described in
KB-article 835680 and happen until now only on the customers server, where we
do not have direct access. Additionally, the customer can not change from
Windows 2000 to Windows 2003, the preferred solution.
Now we first want to make sure that it really is the described bug, that was
announced in technical preview of .net 1.1 to be solved with current SP1.
1. How can one detect 835680 easily and without doubt (special log-entry,
debug, ...)?
2. This issue is not mentioned any more to be solved in release-version of
SP1. Is it fixed ?
Thanks
we are experiencing severe problems within a rollout of an
asp.net-application. The symptoms are very similay to the ones described in
KB-article 835680 and happen until now only on the customers server, where we
do not have direct access. Additionally, the customer can not change from
Windows 2000 to Windows 2003, the preferred solution.
Now we first want to make sure that it really is the described bug, that was
announced in technical preview of .net 1.1 to be solved with current SP1.
1. How can one detect 835680 easily and without doubt (special log-entry,
debug, ...)?
2. This issue is not mentioned any more to be solved in release-version of
SP1. Is it fixed ?
Thanks