Re: after sharepoint 2.0 update

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Brandy,

you again mention Service pack 1 below, but, this is already at service pack
2. Is this version issue not corrected in service pack 2? I don't see
anywhere in site settings, a way to look at the version number.



""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:xG2uL7fCGHA.1236@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello Mike,
>
> Thank you for posting back!
>
> I am sorry for the delayed response due to weekend. Please understand that
> the newsgroups are staffed weekdays by Microsoft Support professionals to
> answer your systems and applications questions. Your understanding is
> greatly appreciated!
>
> We use the Stsadm.exe command-line tool to force an upgrade of the content
> databases. Please seefollowing KB article for reference:
>
> The version number that is in Site Settings is not updated to 6.0.2.6361
> after you install Windows SharePoint Services Service Pack 1
> http://support.microsoft.com/?kbid=871149
>
> Due to complicated of the issue, I am still doing research on the issue.
> If I have any results, I will update you ASAP. Thanks a lot for your time
> and understanding!
>
> Best regards,
>
> Brandy Nee
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> --------------------
>>Reply-To: "MikeR" <research@xxxxxxxxxxxxxxxxxx>
>>From: "MikeR" <research@xxxxxxxxxxxxxxxxxx>
>>References: <OPXtColBGHA.628@xxxxxxxxxxxxxxxxxxxx>
> <MYfpc2rBGHA.3992@xxxxxxxxxxxxxxxxxxxxx>
> <#D72bxsBGHA.3604@xxxxxxxxxxxxxxxxxxxx>
> <DrZ2ZDuBGHA.832@xxxxxxxxxxxxxxxxxxxxx>
> <u7yA6cxBGHA.4004@xxxxxxxxxxxxxxxxxxxx>
> <#jBk0P6BGHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>>Subject: Re: after sharepoint 2.0 update
>>Date: Fri, 23 Dec 2005 11:26:46 -0800
>>Lines: 172
>>Organization: my own
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>Message-ID: <OxsuRb$BGHA.228@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: rollesolutions.com 66.92.0.119
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:232234
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>Hi Brandy
>>Merry Christmas and Happy New Year to you as well!!
>>
>>Again, I think this is the appropriate group because it relates to the
>>Sharepoint update (
>>Windows SharePoint Services Service Pack 2 (KB887624)) performed on
> 11/24/05
>>I am not using sharepoint with mssql. Am using the MSDE instance. There
>>isn't even 100mb worth of data there so size isn't a problem. What does
> the
>>command line suggestion that you offered do? Before I do it I would like
> to
>>understand it.
>>
>>Again...very important to remember...this happened at the time of the
> update
>>listed above. What occurs during that upgrade? Specifically regarding
>>permissions either in the IIS end or the NTFS end? Possibly file path
>>changes?
>>
>>I do not know how to check the database size for the MSDE but again, I am
>>sure that it is not over 100mb.
>>
>>Thanks,
>>
>>Mike
>>
>>""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>news:%23jBk0P6BGHA.1240@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hello Mike,
>>>
>>> Merry Christmas and Happy New Year!
>>>
>>> Thank you for posting back!
>>>
>>> Mike, actually, from the issue symptom, the issue seems to be more
> related
>>> to Windows SharePoint Service (WSS). The reason why we recommend
> customers
>>> that post in appropriate Newsgroup is you will gain the most qualified
>>> support and solve the issue more efficiency.
>>>
>>> If you still prefer to working in our Newsgroup, surely, I am glad to!
>>>
>>> I have performed a lot of research on your issue, and discussed with the
>>> engineers in SharePoint Newsgroup. The issue can be caused by varies of
>>> factors. Please see my following suggestions:
>>>
>>> ==============
>>>
>>> Suggestion 1:
>>>
>>> Login as a user NOT as an Administrator.
>>>
>>> 1) Go to Command Prompt (Start - Run - cmd).
>>>
>>> 2) <Drive:>\Program Files\Common Files\Microsoft Shared\WebServer
>>> Extensions\60\BIN.
>>>
>>> 3) type the command:
>>>
>>> stsadm -o upgrade -forceupgrade (Press Enter)
>>>
>>> 4) Wait for some time (Until successfull... message).
>>>
>>> 5) Restart the system.
>>>
>>> Suggestion 2:
>>>
>>> Please double check if the SQL database is configured with a size limit
>>> and
>>> the limit is reached. If so, please try raising the limit and then
>>> upload
>>> again,
>>>
>>> NOTE: MSDE by default has a 2 GB limit for the database.
>>>
>>> If it is not the database size issue, I suggest we click "Modify
>>> settings
>>> and columns" in "Shared Documents" and check if there are any duplicated
>>> fields. If so, please remove one and then upload again.
>>>
>>> Also, please check if the certain port is blocked between SharePoint
>>> server
>>> and SQL server, for example, port 1433. If so, please enable it and
> upload
>>> again.
>>>
>>> Please take your time to perform the steps. If you have any updates,
>>> please
>>> feel free to let me know. I am looking forward to hearing from you!
>>>
>>> Best regards,
>>>
>>> Brandy Nee
>>>
>>> Microsoft CSS Online Newsgroup Support
>>>
>>> Get Secure! - www.microsoft.com/security
>>> ======================================================
>>> This newsgroup only focuses on SBS technical issues. If you have issues
>>> regarding other Microsoft products, you'd better post in the
> corresponding
>>> newsgroups so that they can be resolved in an efficient and timely
> manner.
>>> You can locate the newsgroup here:
>>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>>
>>> When opening a new thread via the web interface, we recommend you check
>>> the
>>> "Notify me of replies" box to receive e-mail notifications when there
>>> are
>>> any updates in your thread. When responding to posts via your
>>> newsreader,
>>> please "Reply to Group" so that others may learn and benefit from your
>>> issue.
>>>
>>> Microsoft engineers can only focus on one issue per thread. Although we
>>> provide other information for your reference, we recommend you post
>>> different incidents in different threads to keep the thread clean. In
>>> doing
>>> so, it will ensure your issues are resolved in a timely manner.
>>>
>>> For urgent issues, you may want to contact Microsoft CSS directly.
>>> Please
>>> check http://support.microsoft.com for regional support phone numbers.
>>>
>>> Any input or comments in this thread are highly appreciated.
>>> ======================================================
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>>
>>> --------------------
>>>>Reply-To: "MikeR" <research@xxxxxxxxxxxxxxxxxx>
>>>>From: "MikeR" <research@xxxxxxxxxxxxxxxxxx>
>>>>References: <OPXtColBGHA.628@xxxxxxxxxxxxxxxxxxxx>
>>> <MYfpc2rBGHA.3992@xxxxxxxxxxxxxxxxxxxxx>
>>> <#D72bxsBGHA.3604@xxxxxxxxxxxxxxxxxxxx>
>>> <DrZ2ZDuBGHA.832@xxxxxxxxxxxxxxxxxxxxx>
>>>>Subject: Re: after sharepoint 2.0 update
>>>>Date: Thu, 22 Dec 2005 08:46:14 -0800
>>>>Lines: 176
>>>>Organization: my own
>>>>X-Priority: 3
>>>>X-MSMail-Priority: Normal
>>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>>>X-RFC2646: Format=Flowed; Original
>>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>>>Message-ID: <u7yA6cxBGHA.4004@xxxxxxxxxxxxxxxxxxxx>
>>>>Newsgroups: microsoft.public.windows.server.sbs
>>>>NNTP-Posting-Host: rollesolutions.com 66.92.0.119
>>>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>>>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:232009
>>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>>
>>>>Hi brandy,
>>>>
>>>>I was going to say that I politely disagree but Susan beat me to it. I
>>> think
>>>>this is appropriately posted here as it relates to SBS03 and a very
> recent
>>>>windows update.
>>>>
>>>>Can anyone look at their permissions on the IIS end and let me know if
>>> only
>>>>read and directory browsing are checked? I wouldn't expect an update to
>>> have
>>>>changed something there but can't hurt to check.
>>>>
>>>>Again...I can add a document to the library but I cannot change it once
> it
>>>>is there and I used to be able to do that before that update.
>>>>
>>>>Does anyone know which account companyweb uses when accessing the actual
>>>>directory? Is it using the actual user account of the person accessing
>>>>sharepoint?
>>>>
>>>>Thanks,
>>>>
>>>>Mike
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>


.

Relevant Pages

  • RE: SBS2k3 SP1 upgrade
    ... please run the Service Pack installation again. ... from the SBS server box and then try to apply the Windows 2003 sp1. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: "Microsoft Windows SharePoint Services 3.0 setup did not complete successfully" on SBS 2003
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... | Subject: Re: "Microsoft Windows SharePoint Services 3.0 setup did not ...
    (microsoft.public.windows.server.sbs)
  • RE: problems with connecting to our internal company website
    ... synchronize the Windows SharePoint Services Timer ... Configure virtual server for central administration under Server ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Server 2003 Service Pack 1 will not install
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... <Subject: Re: Windows Server 2003 Service Pack 1 will not install ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS sp1 upgrade failed
    ... MSDE 2000 Service Pack 4 did not install and fax configuration. ... Please use the following method to check the service pack level. ... Download MSDE SP4 from Microsoft Download, ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)