RE: Companyweb sts_config error with event id 1000 50070

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

Hello DirkHedlund,

Thank you for posting back!

I understand that you got 6013 error ID when you running Backup. I suggest
you that install the hotfix in the following KB article to fix the issue.
Please see:

833167 A Volume Shadow Copy Service (VSS) update package is available for
http://support.microsoft.com/?id=833167

For your original issue, please help to gather more detail log files for
further research:

1. On the server, go to %system root%\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs\setup. Copy and paste
the full content of the setup file to the Newsgroup.

2. On the server, go to %system root%\Program Files\Microsoft SQL
Server\MSSQL%SHAREPOINT\LOG\ERRORLOG. Copy and paste the full content of
the ERRORLOG to the Newsgroup.

3. In my last reply, "## Determine which instances are accessible on the
server, step 3", what is the output after you run the command "Osql -E -S
<computername>\<instance name>"? Please copy and paste the full result to
the Newsgroup.

I am greatly appreciated your time and co-operation, and am looking forward
to hearing from you soon!

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.



--------------------
>Thread-Topic: Companyweb sts_config error with event id 1000 50070
>thread-index: AcWvJmczouUx0X5qSUWJDCgCClPEyw==
>X-WBNR-Posting-Host: 67.41.107.74
>From: =?Utf-8?B?RGlyayBIZWRsdW5k?= <DirkHedlund@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <DBF37F58-6B70-472D-851F-BD396802886E@xxxxxxxxxxxxx>
<jkga2nTrFHA.1204@xxxxxxxxxxxxxxxxxxxxx>
<5165266C-EFE9-4186-878D-22A36338BF57@xxxxxxxxxxxxx>
<zQeabVgrFHA.3932@xxxxxxxxxxxxxxxxxxxxx>
<69C8C444-E65D-4385-A900-021715A5AA13@xxxxxxxxxxxxx>
<bsaNKosrFHA.1208@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Companyweb sts_config error with event id 1000 50070
>Date: Thu, 1 Sep 2005 11:53:12 -0700
>Lines: 192
>Message-ID: <D9DC6FF8-16D9-4843-9B97-0D5F6E20F2B3@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:150001
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Brandy, thanks for the reply.
>
>I managed to get through the list down to the part that says "##Restart
>Sharepoint service:"; After that, I'm a bit confused. I found all the MDF
>and LDF files, but I do not see the files listed in step 4. Are they
found
>somewhere else?
>
>Also, I don't want to throw a red herring into this process, but I noticed
>that my backups are failing and VSS is listing a SQL error of some sort.
I
>thought *maybe* it could be related (or not). Here's THAT error:
>
>Event Type: Error
>Event Source: VSS
>Event Category: None
>Event ID: 6013
>Date: 9/1/2005
>Time: 1:29:55 PM
>User: N/A
>Computer: SERVER1
>Description:
>Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize.
hr
>= 0x80004005. SQLSTATE: 08001, Native Error: 17
>Error state: 1, Severity: 16
>Source: Microsoft OLE DB Provider for SQL Server
>Error message: [DBNETLIB]SQL Server does not exist or access denied.
>
>
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 2d 20 43 6f 64 65 3a 20 - Code:
>0008: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
>0010: 30 30 30 30 30 34 39 31 00000491
>0018: 2d 20 43 61 6c 6c 3a 20 - Call:
>0020: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
>0028: 30 30 30 30 30 33 39 37 00000397
>0030: 2d 20 50 49 44 3a 20 20 - PID:
>0038: 30 30 30 30 39 30 32 38 00009028
>0040: 2d 20 54 49 44 3a 20 20 - TID:
>0048: 30 30 30 30 38 32 35 36 00008256
>0050: 2d 20 43 4d 44 3a 20 20 - CMD:
>0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
>0060: 57 53 5c 53 79 73 74 65 WS\Syste
>0068: 6d 33 32 5c 76 73 73 76 m32\vssv
>0070: 63 2e 65 78 65 20 20 20 c.exe
>0078: 2d 20 55 73 65 72 3a 20 - User:
>0080: 4e 54 20 41 55 54 48 4f NT AUTHO
>0088: 52 49 54 59 5c 53 59 53 RITY\SYS
>0090: 54 45 4d 20 20 20 20 20 TEM
>0098: 2d 20 53 69 64 3a 20 20 - Sid:
>00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18
>
>
>""Brandy Nee [MSFT]"" wrote:
>
>> Hello DirkHedlund,
>>
>> Thank you for posting back!
>>
>> I have performed further research on your issue, and I got some
additional
>> information for you. Please take your time to perform the following
steps
>> because it is a bit long. Please understand that we may need to
reinstall
>> the companyweb if it is necessary.
>>
>> Based on my research, this problem may occur if there are two SQL Server
>> client aliases. We have seen this issue while NETIQ is installed. The
>> aliases were forcing all connections to use Named Pipes or TCP/IP. As
WMSDE
>> only listens on Shared Memory (not Named Pipes or TCP/IP), all
connections
>> failed.
>>
>> I suggest that we do the following:
>>
>> ## Determine which instances are accessible on the server
>>
>> 1. Go to Start -> Run "services.msc" (without quotation marks).
>>
>> 2. Determing the instances running on your machine by looking for
>> MSSQL$<instance name> (for example, MSSQL$SHAREPOINT)
>>
>> 3. Use the osql command to attempt to connect to the instance by typing
the
>> following command at a command prompt:
>>
>> Osql -E -S <computername>\<instance name>
>>
>> ## Ensure that the service for tha Instance is started
>>
>> 1. Go to Start -> Run "services.msc" (without quotation marks).
>>
>> 2. Confirm that the service, for the instance in question, is started.
>>
>> 3. If it is disabled, set it to automatic and start the service.
>>
>> ##Verify That IIS Is Not Running in IIS 5.0 Isolation Mode
>>
>> 1. Click "Start", point to "Programs", point to "Administrative Tools",
and
>> then click "Internet Information Services (IIS) Manager".
>>
>> 2. In the left pane, right-click your server name, and then expand the
>> local computer.
>>
>> 3. Right click "Web Sites", and then click Properties.
>>
>> 4. Click the "Service" tab.
>>
>> 5. Click to clear the "Run WWW service in IIS 5.0 isolation mode" check
box.
>>
>> 6. Click "OK"
>>
>> 7. To start the WWW service, click "Yes".
>>
>> ##Remove any other aliases
>>
>> 1. Use the SQL Server Client Network Utility (Start -> Run. Type
cliconfg
>> and click OK.) to remove all aliases for the SQL Server instance you are
>> trying to connect to. To launch the SQL Server Client Network Utility
by
>> doing the following:
>>
>> a. Go to start\run command line
>>
>> b. Type the following command: cliconfg
>>
>> c. It launched the SQL Server Client Network Utility dialog box
>>
>> d. In the General Tab, make sure that TCP/IP and Named Pipes protocols
are
>> enabled. Also, make sure that the option of "Enable Shared Memory
Protocol"
>> is enabled. Make sure that no other protocol is enabled and the option
of
>> "force protocol encryption" is not selected.
>>
>> e. Select the Alias tab and if there is a named instance to SQL server,
>> deleted this entry and select APPLY button
>>
>> 2. You may also double-check the registry key
>> HKLM\Software\Microsoft\MSSQLServer\Client\ConnectTo (this contains the
>> Aliases displayed in the SQL Server Client Network Utility) for any
value
>> with the name of your instance, and Data starting with "DBNMPNTW" (a
Named
>> Pipes alias) or "DBMSSOCN" (a TCP/IP alias)
>>
>> 3. Type the following command in command prompt:
>>
>> osql -s twd-iis04\sharepoint -E
>>
>> 4. Open IIS manager console, expand the Application Pools folder, make
sure
>> that all the application pools are started. Then click Start -> Run,
type
>> Services.msc, select the "Sharepoint Timer Service", make sure that it
logs
>> on by the NT Authority\Network Service account.
>>
>> 5. Restart the IIS Server by IISRESET command or from the IIS manager
>> console.
>>
>> ##Check file's permission:
>>
>> 1. Check file permissions on C:\Program Files\Common Files\System\Ole
>> DB\oledb32.dll to make sure it has the following settings:
>>
>> Administrators (Full Control)
>> SYSTEM (Full Control)
>> Users (Read & Execute)
>>
>> ##Sync System Time:
>>
>> This issue will also occurred by the time screw in the domain, so please
>> synchronize the time on all computers within the domain using:
>>
>> net time \\[SBS Server Name] /domain:[Domain Name] /set
>>
>> ##Restart Sharepoint service:
>>
>> 1. Open Windows Explorer
>>
>> 2. Browse to C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data
>>
>> 3. Move all *.MDF files and all *.LDF files
>>
>> 4. Rename the following files to the correct names:
>>
>> master$4idr -> master.mdf
>> mastlog$4idr -> mastlog.ldf
>> model$4idr -> model.mdf
>> modellog$4idr -> modellog.ldf
>> msdbdata$4idr -> msdbdata.mdf
>> msdblog$4idr -> msdblog.ldf
>>
>> Then start the MSSQL$SHAREPOINT services to see if the issue is resolved.
>>
>> I am greatly appreciated your time and co-operation. If anything is
>> unclear, please feel free to let me know. I am looking forward to
hearing
>> from you!
>>
>> Best regards,
>>
>> Brandy Nee
>
>

.

Quantcast