Problem of realization replication through WEB

Hello

There is a following mistake at replication through WEB

A security error occurred

I try to go through IE which user has specified in the master of creation of the subscriber, in a diagnostic mode

https://Servak/Replication/replisapi.dll?diag

And all works, all certificates fulfil correctly who did not collide{face} in what business? WHERE TO DIG?

The name of the server on the certificate and the one you are using in the URL do not match. Hence the error.

It could also be that the the certificate is issued to machine.domain and you are using only machine in the URL. Please use the domain name and try again.

Match up the names on both and retry. Let me know if you continue to see the error.

|||

Certification all has adjusted as it is told BOL

The circuit has turned out such

http://replication2006.narod.ru/index.html

All the same deduces this mistake A security error occurred

The certificate signed the center of certification which has requested with IIS, has established the server certificate both on a server and on the client, and even having given{allowed} unlimited rights to participants of the circuit, it is impossible. Help! In what there can be a mistake? Where to dig?

|||

Here the text of a mistake from JOB

I enter this URL the address in IE all Ок!!

Help!

Selected row details:

Log Job History (REPL-GisisTerminalClient_RED-ReplTerm-SHEIN-GisisTerminalClient_RED- 0)

Step ID 1
Server SHEIN
Job Name REPL-GisisTerminalClient_RED-ReplTerm-SHEIN-GisisTerminalClient_RED- 0
Step Name Run agent.
Duration 00:00:31

Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
-XSTEPID 1
-XSUBSYSTEM Merge
-XSERVER SHEIN

-XCMDLINE 0
-XCancelEventHandle 00000634
2006-11-14 15:14:12.578 Connecting to Subscriber 'SHEIN'
2006-11-14 15:14:12.906 Connecting to Subscriber 'SHEIN'
2006-11-14 15:14:13.062 The upload message to be sent to Publisher 'REPL' is being generated
2006-11-14 15:14:13.078 The merge process is using Exchange ID '7AA8372B-F9E6-4F43-99AB-7C49614D2528' for this web synchronization session.

2006-11-14 15:14:28.500 A security error occurred

2006-11-14 15:14:28.546 Category:NULL
Source: Merge Process
Number: -2147209329

Message: A security error occurred

2006-11-14 15:14:28.546 Category:NULL
Source: Merge Process(Web Sync Client)
Number: -2147010889
Message: The Merge Agent could not connect to the URL 'https://repl/ReplWeb/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and tha

Web server is reachable.

|||

Sorry, I dont understand from your reply whether the name of the server on the certificate matches the one on InternetURL in the merge agent.

I see in the job that you have: 'https://repl/ReplWeb/replisapi.dll'

Is the certificate issued to machine "repl"?

Is there domain name also on the certificate? If so, please try using that in the job parameter.

Have you installed the certificate on the client?

Security error is always a result of mismatch or the client does not trust the certificate.

|||

YES, I do{make} inquiry about receptions of the certificate from a computer repl, on a computer repl it is established IISб I sign the made inquiry in the center of certification and I transfer{pass} on repl signed by the center of certification the certificate and the root certificate cent Ра of certification, I install in IE the root certificate, and the certificate signed IIS I fix{establish} for adjustment{option} of encoding SSL, On the client I transfer{pass} the root certificate of the center of certification and I install it{him} with help IE

IE - tools - internet options - content - certificates - trusted root Certification Authorities - import

For check on the client I collect{type}:

<https://shein/ReplGAI/replisapi.dll?diag>

Any problems does not arise at once the window where it is necessary to enter Login and Password is deduced, I receive page:

http://replication2006.narod.ru/TestReplisapi.html

|||Are you saying the problem is now fixed or still have the issue?|||

No. The problem is!

Load a file, I there on steps have described and have drawn a problem. Thanks big that help me!!!

http://www.replication2006.narod.ru/Problem.rar

problem installing Sql Server SP4

Hello,
I am getting the following error message when installing sp4 on a 2nd
instance of sql server 2k on a win2003 server
"Specified file cannot be opened as write. Ensure file is not is use and
restart setup
C:\Program Files\Sql Server\80\Shared\msxmlsql.dll"
I rebooted the server and still get the same error message. When I click OK
on the error message sp4 setup shuts down. Any suggestions appreciated what
I can do to get around this problem.
Thanks,
RichI fixed the problem. Turns out that I had a 2nd instance (a new instance of
sql server running). I had to shut down the first instance. THat was what
was using the file below. I was then able to lnstall sp4.
"Rich" wrote:

> Hello,
> I am getting the following error message when installing sp4 on a 2nd
> instance of sql server 2k on a win2003 server
> "Specified file cannot be opened as write. Ensure file is not is use and
> restart setup
> C:\Program Files\Sql Server\80\Shared\msxmlsql.dll"
> I rebooted the server and still get the same error message. When I click
OK
> on the error message sp4 setup shuts down. Any suggestions appreciated wh
at
> I can do to get around this problem.
> Thanks,
> Rich

Problem installing some components SQL 2005

Hi,

I'm having trouble installing SQL2005 completely. I get a message:
"A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component."

It concerns "Integration services", "Notification services" and "Workstation Components, Books Online and Development Tools"

What should I do?

Regards,
Ronald

Here is the complete listing of summary.txt:

Microsoft SQL Server 2005 9.00.1399.06

==============================

OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)

Time : Sat Nov 12 21:29:32 2005

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_1.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_1.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_1.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_1.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_2.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_2.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_2.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_2.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_2.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_3.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_3.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_3.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_4.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_3.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_4.log

--

Machine : VL023188

Product : Microsoft SQL Server VSS Writer

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SqlWriter_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_4.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_3.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_5.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_4.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_5.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Books Online (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BOL_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_5.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_4.log

--

Machine : VL023188

Product : Integration Services

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Integration Services

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_DTS.log

Error Number : 1603

--

Machine : VL023188

Product : SQLXML4

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLXML4_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQL.log

--

Machine : VL023188

Product : SQLXML4

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLXML4_2.log

--

Machine : VL023188

Product : Notification Services

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Notification Services

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_NS.log

Error Number : 1603

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Reporting Services

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_RS.log

--

Machine : VL023188

Product : Workstation Components, Books Online and Development Tools

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Tools

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_Tools.log

Error Number : 1603

--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Let's start by looking at what's already installed on your machine. The error you're getting usually means the component is already installed. To figure out what's installed, go to Add/Remove Programs and find the entry for "SQL Server 2005". Select that entry and click Change. Once the dialog appears you should see a button named "Report". Click that button and you'll get a report detailing your installation. Select the contents of that report and copy/paste them into a reply here. Once we determine what you have installed we can figure out what you need to do.

Dan|||

Below the output of "Report". I also found out that there are a number of CTP rows in the add/remove software list. I thought I removed all SQL components but this morning after rebooting I discovered these components and I don't know where they come from. I have installed VS2005 also after installing SQL2005. Should I remove those CTP components? And in what order?
Perhaps you should also know that I removed all SQL branches in the registry (9.00....) because the installation of SQL2005 wouldn't start.
VL023188

The following components are installed on this server

MSSQLSERVER

Analysis Services

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

Database Engine

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

Reporting Services

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

SQLEXPRESS

Database Engine

[Version: 9.00.1399.06 Edition: Express Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

|||

Well, I managed to uninstall most of the CTP components. Just one is left that I cannot uninstall: Microsoft SQL Server Tools CTP. This one is looking into a directory that doesn't exist anymore. I can see that it was the SQL 2005 September CTP enterprise edition but I don't have that one anymore (also not available for subscribers?). How can I uninstall this one?

|||I found out that the report services weren't functioning very well (I was not able to open an existing report project). So I uninstalled the component reporting services (in add/remove, change on SQL2005). But after that I am not able to reinstall reporting services because:

Machine : VL023188
Product : Reporting Services

Error : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
-
Machine : VL023188
Product : Microsoft SQL Server 2005 Reporting Services
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0023_VL023188_RS.log
Last Action : DetectInstanceClash
Error String : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Error Number : 28086
-

What to do?

|||

Plenty wrote:

Well, I managed to uninstall most of the CTP components. Just one is left that I cannot uninstall: Microsoft SQL Server Tools CTP. This one is looking into a directory that doesn't exist anymore. I can see that it was the SQL 2005 September CTP enterprise edition but I don't have that one anymore (also not available for subscribers?). How can I uninstall this one?

I got a solution for this problem:
http://blogs.msdn.com/brada/archive/2005/06/24/432209.aspx

This helped me, now I could install the tools

But the one above still isn't solved (reporting services, existing instance). How can I remove that exsiting instance?|||

Try the following:

1. Kill the service with command sc if it still exists.

2. Go to Registry editor, remove those registy keys related to the service. You need to search the whole regisgtry tree.

3. Reboot the machine.

Problem installing MSDE

I must be doing something wrong here, i have downloaded msde and when i run the set up i get this error

The instance name specified is invalid.

Any ideasInstance Names -- Rules from BOL:

Instance Name

Enter a new instance name, or the name of the instance to maintain. Review and follow the rules for instance names.

Important It is recommended that instance names be kept to less than 10 characters. Instance names can appear in the user interface of various SQL Server and system tools; shorter names are more readable.

Instance Naming Rules

An instance name is not case-sensitive.

An instance name cannot be the terms Default or MSSQLServer.

Instance names must follow the rules for SQL Server identifiers and cannot be reserved keywords.

Instance names are limited to 16 characters.

The first character in the instance name must be a letter, an ampersand (&), an underscore (_), or a number sign (#). Acceptable letters are those defined by the Unicode Standard 2.0, which includes Latin characters a-z and A-Z, in addition to letter characters from other languages.

Subsequent characters can be:
Letters as defined in the Unicode Standard 2.0.

Decimal numbers from either Basic Latin or other national scripts.

The dollar sign ($), a number sign (#), or an underscore (_).
Embedded spaces or special characters are not allowed in instance names. Neither is the backslash (\), a comma (,), a colon (:), or the at sign (@.).

Warning Only characters that are valid in the current Microsoft Windows® code page can be used in instance names in SQL Server 2000. If a Unicode character not supported under the current code page is used, an error occurs.|||Thanks for the informative reply but it doens't mean anything to me. Sorry dumb user here. I haven't specified any names, just clicked on the setup file|||using the DOS command prompt chage directory to where you have unzipped the setup files to, ie: on my computer its C:\sql2ksp3\MSDE. Below is a snippet of the readme file that will help you out.

To install a new instance of Desktop Engine

Open a command prompt window.

From the command prompt, use the cd command to navigate to the folder containing the MSDE 2000 SP3a setup utility:
cd c:\MSDESP3aFolder\MSDE

where c:\MSDESP3aFolder is either the path to the folder into which you extracted the MSDE 2000 SP3a files, or the Desktop Engine SP3a folder on the SQL Server 2000 SP3a CD.

Execute one of the following commands:
To install a default instance configured to use Windows Authentication Mode, execute:
setup SAPWD="AStrongSAPwd"
Where AStrongSAPwd is a strong password to be assigned to the sa login.

To install a named instance configured to use Windows Authentication Mode, execute:
setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
Where AStrongSAPwd is a strong password to be assigned to the sa login and InstanceName is the name to be assigned to the instance.

To install a default instance configured to use Mixed Mode, execute:
setup SAPWD="AStrongSAPwd" SECURITYMODE=SQL
Where AStrongSAPwd is a strong password to be assigned to the sa login.

To install a named instance configured to use Mixed Mode, execute:
setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd"|||Follow this:

I post this as I have tried to install MSDE sp 3 and configure it to work with Quickstart however it seems that that tasks is so difficult to do so I hope by posting it here. I can help many people who wants to solve this problem

Here is how I install the MSDE and configure it to run with quick start

Note:
1. First extract the MSDE which is download from Microsoft to C:\MSDE

2. Once installing MSDE restart and run your MSDE service
by typing net start MSSQL$NETSDK
on the command prompt and then type osql -L to see if there is any server running
3. Becareful in the second script if there is any ANDY-XP. That's my computer name, unfortunately I could not change that using %COMPUTERNAME% variable so I just leave it as it is. Remember to change it as appropriate

then Create two batch scripst:
==============================================
First batch script
==============================================
@.echo off
REM Follow these instructions for installing MSDE 2000 Sp 3:
REM You must firstly extract the MSDE setup files on C:\MSDE folder for this script to work
REM Define Variables

set MSDE_HOME = C:\MSDE
%MSDE_HOME%\Setup.exe INSTANCENAME=NetSDK SAPWD=password

REM (Once installing, please restart your computer first)

pause

save it as Setup MSDE.bat
==============================================
The second batch script
================================================
@.echo off
REM To install northwind database for the quickstart tutorial. Follow these steps

REM Define variable
SET SAMPLE_SETUP_PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Samples\Setup

REM start the MSSQL$NETSDK
net start MSSQL$NETSDK

REM Seeing whether the server running
osql -L
REM if response is none then make sure that your server MSDE instance name NetSDK is running

cd %SAMPLE_SETUP_PATH%

c:

osql -E -S ANDY-XP\NetSDK -i InstNwnd.sql

osql -E -S ANDY-XP\NetSDK -i Grocer.sql

osql -E -S ANDY-XP\NetSDK -i instpubs.sql

osql -E -S ANDY-XP\NetSDK -i Portal.sql

REM After installing the NorthWind database, you still need to add the role user and assigned permission to it

REM Look on the C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Samples\Setup\html\ConfigDetails.htm for configuring database

osql -E -S %COMPUTERNAME%\NetSDK -Q "sp_grantlogin '%COMPUTERNAME%\ASPNET'"

osql -E -S %COMPUTERNAME%\NetSDK -d Pubs -Q "sp_grantdbaccess '%COMPUTERNAME%\ASPNET'"
osql -E -S %COMPUTERNAME%\NetSDK -d Pubs -Q "sp_addrolemember 'db_owner', '%COMPUTERNAME%\ASPNET'"

osql -E -S %COMPUTERNAME%\NetSDK -d NorthWind -Q "sp_grantdbaccess '%COMPUTERNAME%\ASPNET'"
osql -E -S %COMPUTERNAME%\NetSDK -d NorthWind -Q "sp_addrolemember 'db_owner', '%COMPUTERNAME%\ASPNET'"

osql -E -S %COMPUTERNAME%\NetSDK -d Portal -Q "sp_grantdbaccess '%COMPUTERNAME%\ASPNET'"
osql -E -S %COMPUTERNAME%\NetSDK -d Portal -Q "sp_addrolemember 'db_owner', '%COMPUTERNAME%\ASPNET'"

osql -E -S %COMPUTERNAME%\NetSDK -d GrocerToGo -Q "sp_grantdbaccess '%COMPUTERNAME%\ASPNET'"
osql -E -S %COMPUTERNAME%\NetSDK -d GrocerToGo -Q "sp_addrolemember 'db_owner', '%COMPUTERNAME%\ASPNET'"

pause

save it as Configure MSDE and database.bat
==============================================

Then run the first and followed by the second batch script

Have a try and let me know if there is a mistakes on it. Any improvements can be sent to triandy_gunawan@.yahoo.com.|||Thanks guys it gathered all the info. Is that wat i need to do?|||I run it from this link
http://www.asp.net/msde/Default.aspx?tabindex=0&tabid=1

Will this give me msde. seems to be an upgrade but didn't have it in the first place|||See the link bellow for help installing MSDE

Sql Server Installation Options

Hope this helps.

Regards

Wayne Phipps|||Thanks mate. SO when is running i get a little sign on the toolbar next to the time, with a play sign in it. mssql server?|||Your partly correct but its actually the Icon for the Service Manager which allows you to start/stop an Instance of SQL Server.

If you have more than one instance of SQL Server Installed, you can double click the icon and select the specific server from the dropdown list.

Hope this helps.

Regards

Wayne Phipps