Prev: XP Clients and power options
Next: Windows SBS 2008 domain purchase and configuration wiza has stoppe
From: David Parkes on 4 Jun 2010 06:52
Hi Robbin,

Thanks for letting me know. I really appreciate the time you and others
spend on help me with this issue.

Kind Regards

David

""Robbin Meng [MSFT]"" <v-robmen(a)online.microsoft.com> wrote in message
news:8RMk$48ALHA.2364(a)TK2MSFTNGHUB02.phx.gbl...
>
> Hi David,
>
> Thank you for the reply with more detailed information. Currently, I am
> still working on it with further research and will follow up with you as
> soon as possible.
>
> Your time and patience are appreciated.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>
From: David Parkes on 7 Jun 2010 11:44
Hi Robbin,

Have you had any luck with this?

"David Parkes" <wibble(a)wobble.com> wrote in message
news:OX5qOQ9ALHA.5476(a)TK2MSFTNGP06.phx.gbl...
> Hi Robbin,
>
> Thanks for letting me know. I really appreciate the time you and others
> spend on help me with this issue.
>
> Kind Regards
>
> David
>
> ""Robbin Meng [MSFT]"" <v-robmen(a)online.microsoft.com> wrote in message
> news:8RMk$48ALHA.2364(a)TK2MSFTNGHUB02.phx.gbl...
>>
>> Hi David,
>>
>> Thank you for the reply with more detailed information. Currently, I am
>> still working on it with further research and will follow up with you as
>> soon as possible.
>>
>> Your time and patience are appreciated.
>>
>>
>> Best regards,
>> Robbin Meng(MSFT)
>> Microsoft Online Newsgroup Support
>>
>>
From: "Robbin Meng [MSFT]" on 8 Jun 2010 04:20

Hi David,

Sorry for the late in responding you.

Based on your issue symptoms, the error message is "The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal
Database signatures". The possible cause is the SPWebService service has not been fully provisioned. This problem occurs when the initial provisioning of the Web service
instance has not completed successfully. This behavior causes the upgrade process to skip the Web service instance.

So you can see the corresponding solution as we indicated that listed in both KB 944267 and KB 944154 as below:

[Resolution:]
To resolve this problem, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. Locate the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN" folder.
3. At the command prompt, type the following commands, and then press ENTER after each command:
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""
stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""
4. After the SPWebService service is started, type the following command at the command prompt, and then press ENTER:
psconfig -cmd upgrade -inplace b2b -wait -force
Note, the last command force the Windows SharePoint Services 3.0 upgrade by using the Psconfig.exe tool at a command prompt.

Based on your last reply and new information, last Psconfig.exe tool reported error message "Failed to initialize SharePoint Products and Technologies upgrade." and "Failed
to detect if this server is joined to a server farm." during the Performing configuration tasks. To troubleshoot this error message, you may try the solutions in KB926062 and then try
again with Psconfig.exe tool command. However, if the Performing configuration tasks still fails or the issue persists, please try the below steps. Please make sure you have a
good backup of SharePoint content database before you perform further steps to create new web application and attach existing content database.

- Go to SharePoint 3.0 Central Administration > Application Management > Content Databases
- Remove the default database. Remove the content database from Manage content database page for default site.
- Then re-add the same content database from command prompt using STSADM command.
- Following is the command to add content database.
STSADM -o addcontentdb -url <http://servername> -databasename (Provide the Content database name) -databaseserver (database server name, like servername
\microsoft##ssee)
- Once the command completed successfully try to browse the site again.

Note, the syntax for the Stsadm.exe command-line tool with the addcontentdb operation is listed as follows:

stsadm.exe -o addcontentdb -url URL -databasename DatabaseName [ -databaseserver DatabaseServerName ] [ -databaseuser UserName ] [ -databasepassword
Password ] [ -sitewarning SiteWarning ] [ -sitemax SiteMaxCount ]
Note The -url and -databasename parameters are required. The other parameters are optional.

REFERENCES:
====================
Error message when you try to upgrade Windows SharePoint Services 3.0: "Failed to detect if this server is joined to a server farm"
http://support.microsoft.com/kb/926062

Hope it helps.


Sincerely,
Robbin Meng
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================



From: David Parkes on 8 Jun 2010 11:50
Hi Robbin,

Thanks for your reply. When i try and run the following command;

STSADM -o addcontentdb -url http://chanserv -databasename
ShareWebDb -databaseserver CHANSERV\MICROSOFT##SSEE

i get a message that says the following;

The server instance specified was not found. Please specify the server's
address and port

David

""Robbin Meng [MSFT]"" <v-robmen(a)online.microsoft.com> wrote in message
news:qWJJCOuBLHA.4488(a)TK2MSFTNGHUB02.phx.gbl...
>
> Hi David,
>
> Sorry for the late in responding you.
>
> Based on your issue symptoms, the error message is "The database
> WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing
> Windows Internal
> Database signatures". The possible cause is the SPWebService service has
> not been fully provisioned. This problem occurs when the initial
> provisioning of the Web service
> instance has not completed successfully. This behavior causes the upgrade
> process to skip the Web service instance.
>
> So you can see the corresponding solution as we indicated that listed in
> both KB 944267 and KB 944154 as below:
>
> [Resolution:]
> To resolve this problem, follow these steps:
> 1. Click Start, click Run, type cmd, and then click OK.
> 2. Locate the "Program Files\Common Files\Microsoft Shared\Web server
> extensions\12\BIN" folder.
> 3. At the command prompt, type the following commands, and then press
> ENTER after each command:
> stsadm -o provisionservice -action stop -servicetype
> spwebservice -servicename ""
> stsadm -o provisionservice -action start -servicetype
> spwebservice -servicename ""
> 4. After the SPWebService service is started, type the following command
> at the command prompt, and then press ENTER:
> psconfig -cmd upgrade -inplace b2b -wait -force
> Note, the last command force the Windows SharePoint Services 3.0 upgrade
> by using the Psconfig.exe tool at a command prompt.
>
> Based on your last reply and new information, last Psconfig.exe tool
> reported error message "Failed to initialize SharePoint Products and
> Technologies upgrade." and "Failed
> to detect if this server is joined to a server farm." during the
> Performing configuration tasks. To troubleshoot this error message, you
> may try the solutions in KB926062 and then try
> again with Psconfig.exe tool command. However, if the Performing
> configuration tasks still fails or the issue persists, please try the
> below steps. Please make sure you have a
> good backup of SharePoint content database before you perform further
> steps to create new web application and attach existing content database.
>
> - Go to SharePoint 3.0 Central Administration > Application Management >
> Content Databases
> - Remove the default database. Remove the content database from Manage
> content database page for default site.
> - Then re-add the same content database from command prompt using STSADM
> command.
> - Following is the command to add content database.
> STSADM -o addcontentdb -url <http://servername> -databasename (Provide the
> Content database name) -databaseserver (database server name, like
> servername
> \microsoft##ssee)
> - Once the command completed successfully try to browse the site again.
>
> Note, the syntax for the Stsadm.exe command-line tool with the
> addcontentdb operation is listed as follows:
>
> stsadm.exe -o addcontentdb -url URL -databasename DatabaseName
> [ -databaseserver DatabaseServerName ] [ -databaseuser UserName ]
> [ -databasepassword
> Password ] [ -sitewarning SiteWarning ] [ -sitemax SiteMaxCount ]
> Note The -url and -databasename parameters are required. The other
> parameters are optional.
>
> REFERENCES:
> ====================
> Error message when you try to upgrade Windows SharePoint Services 3.0:
> "Failed to detect if this server is joined to a server farm"
> http://support.microsoft.com/kb/926062
>
> Hope it helps.
>
>
> Sincerely,
> Robbin Meng
> Microsoft Online Newsgroup Support
> ==================================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ==================================================================
>
>
>
From: "Robbin Meng [MSFT]" on 9 Jun 2010 10:21


Hi David,

It seems there is some problem with the syntax, please try again with "http://chanserv" (add "")and "ShareWebDb"(add "") for URL and Databasename, also delete the [ -
databaseserver CHANSERV\MICROSOFT##SSEE ] part.

The Stsadm.exe command-line tool with the addcontentdb operation is to re-add the content database. Then, restart the SQL Server 2005 Embedded Edition service. Please refer
to below article for more information:

Error message when you use SharePoint 3.0 Central Administration to try to re-add a content database in Windows SharePoint Services 3.0
http://support.microsoft.com/kb/926961/en-us

Addcontentdb: Stsadm operation (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc288692(office.12).aspx

Top 3 Reasons for the "The server instance specified was not found. Please specify the server's address and port." Error
http://blogs.msdn.com/b/mjeelani/archive/2005/03/05/385816.aspx

Thanks.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================



First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: XP Clients and power options
Next: Windows SBS 2008 domain purchase and configuration wiza has stoppe