Prev: Using SharePoint Designer with WSS 2.0 sites
Next: wss_adminservice.log
From: "Ada Pan [MSFT]" on 15 Dec 2006 01:33
Hello I. Kinal,

I have received your email.

First I am sorry for the wrong link to download the Regmon tool. Here the
correct link: < http://download.sysinternals.com/Files/Regmon.zip >.
Please first download the regmon tool and capture the trace and send me the
log. Thank you for your cooperation.

I am checking for the other logs you sent to me and would like to also
collect the Regmon log from you for further research. Your time and
patience are greatly appreciated.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
From: I. Kinal on 15 Dec 2006 18:19
Hi,

Thank you for your response.

Isn't there any way to use the trace that I already took? It should contain
the same exact data. I just do not want to go through the whole update
process again, as it entails a 2 hour disruption of my production Sharepoint
environment. If I could filter out all of the noise registry activity from
the log, then I could probably get it down to a reasonable size.

Thanks,
I. Kinal

""Ada Pan [MSFT]"" wrote:

> Hello I. Kinal,
>
> I have received your email.
>
> First I am sorry for the wrong link to download the Regmon tool. Here the
> correct link: < http://download.sysinternals.com/Files/Regmon.zip >.
> Please first download the regmon tool and capture the trace and send me the
> log. Thank you for your cooperation.
>
> I am checking for the other logs you sent to me and would like to also
> collect the Regmon log from you for further research. Your time and
> patience are greatly appreciated.
>
> Regards,
>
> Ada Pan
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights
From: "Ada Pan [MSFT]" on 19 Dec 2006 04:35
Hello Brooster,

Based on my knowledge, the error you received could be a different issue
from the original one you encountered. Please understand that the managed
newsgroup is an issue based service, meaning we usually respond to one
question/issue per post. This will lessen the confusion for both of us, as
well as ensure that our results are accurate and not a result of a test for
a different question. Therefore, I will work with you on the first
question in this post. Regarding the additional question, please open a
new post so that the dedicated MS engineer can help you on it in a more
efficient manner.

Let's focus on the first issue in this thread.

Since the new web application doesn't created on the second server, let us
follow the steps to check if all the related services have been started:

1. Open the Central Administration page, click Operation tab.
2. Click Services on server under Topology and Services section,
3. Under the drop down list next to Server, choose the second server in the
farm.
4. Then, make sure Windows SharePoint Services Web Application has been
started.

- If not, click the Start link next to the Windows SharePoint Services Web
Application service.
- If yes, click the Stop link next to the Windows SharePoint Services Web
Application service, and then click Start to re-start the service.

Then, check if create a new web application to check the result.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
From: "Ada Pan [MSFT]" on 19 Dec 2006 04:57
Hello I. Kinal,

Actually, the previous response is for another issue. Please ignore it.

For your issue, please see the information below:

I understand that you may be busy and it is really time-consuming to
reproduce the problem. The reason I recommend you use the Regmon tool is
that I can see some information about what registry keys cannot be accessed
when the problem occurs. However, I am not sure what tool you used to
capture the trace and may have not familiar to analysis such logs. I
appreciate your cooperation and time!

Another work around I would like to provide is that: You can just back up
the configuration and content DBs in WSS 2.0, remove WSS 2.0 and make a
clean install WSS 3.0, and then restore the data to WSS 3.0. For the
instructions, you can refer to the following articles:

Run and test a full backup in SQL Server [Windows SharePoint Services]
http://technet2.microsoft.com/Office/en-us/library/2a005b70-2f53-42a1-89e0-f
907a8e986231033.mspx

Install Windows SharePoint Services 3.0 on a stand-alone computer
http://technet2.microsoft.com/Office/en-us/library/5a39029f-0939-452b-acd2-4
4ff87e7ff711033.mspx?mfr=true

Hope this helps!

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
From: I. Kinal on 20 Dec 2006 21:00
Hi,

I have a question about the workaround that you proposed: is there any
information on how to restore a database backed up from MSDE into SQL 2005
Embedded Edition? Because that is what I would have to do. The second link
that you provided does not lead to the article that you say it should.

Thanks,
I. Kinal

""Ada Pan [MSFT]"" wrote:

> Hello I. Kinal,
>
> Actually, the previous response is for another issue. Please ignore it.
>
> For your issue, please see the information below:
>
> I understand that you may be busy and it is really time-consuming to
> reproduce the problem. The reason I recommend you use the Regmon tool is
> that I can see some information about what registry keys cannot be accessed
> when the problem occurs. However, I am not sure what tool you used to
> capture the trace and may have not familiar to analysis such logs. I
> appreciate your cooperation and time!
>
> Another work around I would like to provide is that: You can just back up
> the configuration and content DBs in WSS 2.0, remove WSS 2.0 and make a
> clean install WSS 3.0, and then restore the data to WSS 3.0. For the
> instructions, you can refer to the following articles:
>
> Run and test a full backup in SQL Server [Windows SharePoint Services]
> http://technet2.microsoft.com/Office/en-us/library/2a005b70-2f53-42a1-89e0-f
> 907a8e986231033.mspx
>
> Install Windows SharePoint Services 3.0 on a stand-alone computer
> http://technet2.microsoft.com/Office/en-us/library/5a39029f-0939-452b-acd2-4
> 4ff87e7ff711033.mspx?mfr=true
>
> Hope this helps!
>
> Regards,
>
> Ada Pan
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Using SharePoint Designer with WSS 2.0 sites
Next: wss_adminservice.log