MwPharm Server Installation - Mediware

screechingagendaΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 10 μήνες)

96 εμφανίσεις

MwPharm 4.0 Server Installation

Jan Muzik, 27.5.2010, Jiří Douša 9.9.2010, updated 30.5.2011

Manual installation of SQL Express server 2008

:

1. Download “SQL Server 2008 Express” installer (32
-
bit or 64
-
bit version) from
http://www.microsoft.com/express/Database/






2. Run “SQL Server 2008 Express” installer and start installation :



3.Set the Acount name and Password (for example set password to “Monteluk
ast”):

4. Specify the password (for example set password to “Montelukast”): for the SQL Server system
administrator (sa) account :

5.Your SQL Server 2008 instalation completed successfully:


6. Run Start
-
>All programs
-
>Microsoft SQL Server 2008
-
>
Configuration Tools
-
>SQL Server Configuration
Manager


7.Enable protocols









8. Restart Server



9. Download installer of server part of MwPharm 4.0 and run installation.


Instalation of MwPharm 4.0 Server :


The content of the installation
folder: run setup.exe

Prerequisites



When you accept both requests Windows Installer 4.5 installation starts.


When it is installer, reboot is required. Click Yes.

When the system reboots and you log in the installation automatically resumes and SQL Se
rver 2008 is
being installed.


It takes about 10minutes.

MwPharm Server Installation






Installation is completed.

Post install

Depending on the computer configuration, you may need to add firewall exception for incoming
connections on TCP port 14
33.


Test


You may run the test.bat file to check that the installation was successful. You should get the following
screen or an error message (if password is not montelukast, edit file “test.bat”).


If test is OK, you can try connect to local server
from client (if you have server and client installed on
same computer) :

A new settings on the client side can be performed in the configuration file c:
\
Program
Files
\
Mediware
\
MwPharm 4.0
\
connection.config, which can be edited through the text editor and
configure the connection string. Examples can be found in the configuration file
connection_string_example.config.



If you can connect to server database from client installed on server you can try to connect to server
from remote client (client on
other PC) :



Possible errors :


Result 0x2, Level16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [2].

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establishing a connection to the server. When conn
ecting to SQL Server
2008
,
this failure may be caused by the fact that under the default settings SQL
Server does not allow remote connections..

Sqlcmd: Error: Microsoft SQL native Client : Login timeout expired

Cause:

When first installed SQL Server 2008
Express Edition does not allow any connections other than
via the Shared Memory protocol on the local machine.

This error can also be caused by firewall settings blocking access to SQL Server.

Possible Remedies:



Enabled Named Pipes and TCP/IP protocols on
the database server.

1.

Start → All Programs → Microsoft SQL Server 2008 → SQL Server Configuration Manager

2.

In the left hand pane, expand "SQL Server Configuration Manager (Local) → SQL Server
2008 Network Configuration"

3.

In the left hand pane, highlight "Pro
tocols for SQLEXPRESS"

4.

In the right hand pane, right click "Named Pipes" and select "Enable"

5.

In the right hand pane, right click "TCP/IP", select "Enable" and then select "Properties"

6.

On the "IP Addresses" tab ensure that "Enabled" is set to "Yes" for each

network adapter
listed.

7.

Click [OK] to close the TCP/IP Properties dialog.

8.

In the left hand pane select "SQL Server 2008 Services"

9.

Right click "SQL Server (SQL EXPRESS)" and select "Restart"

Whilst it is not required for this process, it can make the task
of configuring remote
access to SQL Server Express easier if you also start the process "SQL Server Browser".
You may need to open the properties and on the "Service" tab change the Start Mode
from Disabled to Automatic, before you can start the process.



A
dd SQL Server 2008 Express as an exception to the windows firewall.

You will need to add SQL Server 2008 Express as an exception to any firewall software
that is running locally. The following sequence assumes the Windows XP Firewall:

1.

Start → Control Pane
l (classic view) → Windows Firewall

2.

On the Exceptions tab, click "Add Program..."

3.

Browse to "sqlserver.exe" and click [OK]. This is normally located in the folder "Program
Files
\
Microsoft SQL Server
\
MSSQL.1
\
MSSQL
\
Binn"

4.

Repeat for "sqlbrowser.exe" if you ha
ve set the "SQL Server Browser" service to run. This
is normally located in the folder "Program Files
\
Microsoft SQL Server
\
90
\
Shared"

5.

Click [OK] to close the Windows Firewall dialog.

If you still find that you cannot connect, then try opening TCP Port 1666

in the Windows
Firewall:

6.

Start → Control Panel (classic view) → Windows Firewall

7.

On the Exceptions tab, click "Add Port..."

8.

The "Name" can be anything, but I suggest something like "TCP Port 1666 for SQL
Server". For the "Port number" enter 1666, and ensu
re that TCP is selected. Click [OK]

9.

Click [OK] to close the Windows Firewall dialog.

For those that are interested, the port number 1666 comes from the "TCP Dynamic
Ports" displayed on the "IP Addresses" tab of the "TCP/IP Properties" of the TCP/IP
Protoco
l listed by SQL Server Configuration Manager.

If you get this error when trying to connect using Microsoft SQL Server Management
Studio then try opening UDP port 1434.



Ensure that the SQL Server 2008 Express server process is running.

Check this by:

1.

Start

→ Control Panel (classic view) → Administrative Tools → Services

2.

Scroll down and check that "SQL Server (SQLEXPRESS)" has the status of "Started". Start
it if it is not already started.



Part I


Connection Fail when SNAC connects to Sql Server
2008



U
se osql.exe to simulate the connection string in your application and quick troubleshoot if your
application uses ODBC provider and use sqlcmd.exe for OLEDB provider. They are located in
%SYSTEMDRIVE%
\
Program Files
\
Microsoft Sql Server
\
90
\
tools
\
binn.



Basic connection string:


osql(sqlcmd) /S[prefix]<servername> /E





Osql(sqlcmd) /S[prefix]<servername>
\
<Instance> /E

In each follow Message, there are two, one is from ODBC, and the other one is from OL
EDB.



Message 1
:



[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [
53
].

[SQL Native Client]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to

SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.


-
OR
-



HResult 0x35, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [53].

Error: Micr
osoft SQL Native Client : An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error:
Microsoft SQL Native Client : Login timeout expired.



This indicates that your target server can not be accessed or does not exist. Try to use "ping
<servername>"

, " ping <ipofserver>" , "ping
-
a <ip>", If either of the pings time out, fail, or do
not
return the correct values, then either the DNS lookup is not working properly or there is some
other networking or routing issue that you will need to resolve.



Message 2:



[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL

Serve
r [2].

[SQL Native Client]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to

the server. When connecting to SQL Server 2005, this failure may be caused by

the fact that under the default settings SQL Server do
es not allow remote connections.



-
OR
-



HResult 0x2, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [2].

Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the
server. When con
necting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error: Microsoft SQL Native Client : Login timeout expired.



This error message means that the server was not

found or not running or can not make Named
Pipe connection through the pipe name that client specified. To verify this:



1) From the command line,

do "sc query mssqlserver" or "sc query mssql$<instancename>" to
check whether sql instance present.

Then o
pen sql server configuration manager
-
> check the
state of the sql service, if it is not running, start it. If server started fail, check event log or server
error log, see what happened there.

2)

if you are sure the service is running and shared memory/N
amed Pipe enabled, please try
connection if it is local default instance "osql /Snp:
\
\
.
\
pipe
\
sql
\
query"; or try connection "osql
/Snp:
\
\
.
\
pipe
\
mssql$<InstanceName>
\
sql
\
query" if it is local named instance. if you still get error
2, then go to step 3).

3) D
ouble check the server is started and listening on named pipe if you enabled Named Pipe.
One way is that see the ERRORLOG of the server, search follow keywords:


Server named pipe provider is ready to accept connection on [] or
[
\
\
.
\
pipe
\
mssql$<InstanceNam
e>
\
sql
\
query]


Notice that "sql
\
query" is the default pipe name, so you need to know server is listening on which
pipe name. eg: if you specify server pipe name is "sql
\
query1", then you would see in the errorlog
that server listening on [].


4) See your c
onnection string, whether you explicitly specify the pipe name and does it match the
pipe that server is listening on? Or whether you just specify server name( like ".","(local)", etc),
but you specify the wrong pipe name on client side Named Pipe configur
ation.eg, go to SQL
Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is
same with the one server listening on.


Note: For remote connection, you need to verify step 2) and 3).



Resolution for Message 2: Step
-
by
-
step

1.

Open SQL Server Configuration Manager. Click
Start

-
>
Programs

-
>
Microsoft SQL Server 2008

-
>
Configuration Tools

-
>
SQL Server Configuration Manager
.


2.

On SQL Server Configuration Manager, select
SQL Server Services

on the

left window. If the state
on SQL Server Browser is not running, you have to configure and start the service. Otherwise,
you can skip to step 6.


3.

Double
-
click on SQL Server Browser, the Properties window will show up. Set the account for
start
SQL Server Browser
Service
. In this example, I set to
Local Service

account if you use
Network connection use
Network Service

4.



5.

On SQL Server Browser Properties, move to
Service

tab and change
Start Mode

to
Automatic
.
Therefore, the service will be sta
rt automatically when the computer starts. Click
OK

to apply
changes.


6.

Back to SQL Server Configuration Manager, right
-
click on
SQL Server Bowser

on the right window
and select
Start

to start the service.


7.

On the left window, expand
SQL Server Network Configuration

-
>
P
rotocols for SQLEXPRESS
.
You see that TCP/IP protocol status is disabled.


8.

Right
-
click on
TCP/IP

and select
Enable

to enable the protocol.


9.

There is a pop
-
up shown up that you have to restart the SQL Service to apply changes.


10.

On the left window, select
SQL Server Services
. Select
SQL Server (SQLEXPRESS)

on the right
window
-
> click
Restart
. The SQL Server service will be restarted.


11.

Open Microsoft SQL
Server
Management

Studio and connect to the SQL Server 2008 Express.


12.

Right
-
click on the SQL Server Instance and select
Properties
.


13.

On Server Properties, select
Security

on the left window. Then, select
SQL Server and Windows
Authentication

mode.


14.

Again, there is a pop
-
up show
n up that you have to restart the SQL Service to apply changes.


15.

Right
-
click on the SQL Server Instance and select
Restart
.


16.

That’s it. Now you should be able to connect to the SQL Server 2008 Express remotely.

1)

SQL Server should be up and running.

Go to All Prog
rams >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server
Configuration Manager >> SQL Server Services, and check if SQL Server service status is
“Running”.

In addition, ensure that your remote server is in the same network. Run “sqlcmd
-
L” in

your
command prompt to ascertain if your server is included in your network list. You can even find
tutorial for the same here
SQL SERVER


Find All Servers From Local Network


Using sqlcmd


Detect Installed SQL Server on Network
.

I have confronted numerous situations when these nerve
-
wracking errors crop up, and most of
the time when I try to troubleshoot I notice that SQL Ser
ver services are neither running nor
installed. If SQL Server is not installed as default instance SQL Server Browser should be running
together with it; we will explore this further in Topic 5.


2) Enable TCP/IP in SQL Server Configuration

When two or more SQL Servers are connected across network they do all communication using
TCP/IP. The default port of SQL Server installation is 1433. This port can be changed throu
gh SQL
Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server
Configuration Manager >> Select TCP/IP


Right Click on TCP/IP >> Click on Enable


You must restart SQL Server
Services for all the changes to take effect. Right click and go to
menu properties to select location where default port of SQL Server can be changed.

3) Open Port in Windows Firewall

Windows Firewall is very efficacious in protecting the Operating system
from all sorts of
malicious attacks. By default, many of the ports and services are refrained from running by
firewall. Time and again, SQL Server ports are not open in firewall as well. All the ports on which
SQL Server is running should be added to excep
tion and firewall should filter all the traffic from
those ports. As described, by default SQL Server runs on port 1433, but if default port is changed
then the new port should be added to exception. If SQL Server has named instance (another
instance besid
es default instance) is installed, SQL Server browser should also be added to the
exception, as described in Step 7.

Go to Control Panel >> Windows Firewall >> Change Settings >> Exceptions


>> Add Port



Make the following entries in popup “Add a Port” and click OK.

Name : SQL

Port Number: 1433

Protocol: Select TCP




4) Enable Remote Connection

Enabling remote connection is another important, yet oft
-
ne
glected step that is frequently
missed by database administrators while setting up SQL Server. If this feature is turned off SQL
Server will function smoothly on local machine, but it will let another server connect to it
remotely. By default this feature
is ON in SQL Server 2008.

Right click on the server node and select Properties.


Go to Left Tab of Connections and check “Allow remote connections to this server”


5) Enable SQL Server Browser Service

If SQL Server is not installed as default instance but instead installed as named instance and also
if there is no specific TCP/IP

port configured, it will give rise to the error that is being discussed
in this article. If SQL Server Browser service is enabled, it will allow the server to be connected
through dynamic TCP/IP port. Enabling this service is a one
-
time process, as on ena
bling it once
it will apply to all the instances installed on the same server.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server
Configuration Manager >> SQL Server Browser


Right Click on SQL Server Browser >> Click on Enable

6) Create exception of sqlbrowser.exe in Firewall

As elucidated in Step 6, sqlbrowser service needs to be enabled for named instance. Windows
Firewall may preve
nt sqlbrowser.exe to execute. So, it is imperative to add exception for the
same in windows firewall.

Search for sqlbrowser.exe on your local drive where SQL Server is installed. Copy the path of the
sqlbrowser.exe like C:
\
Program Files
\
Microsoft SQL Serve
r
\
90
\
Shared
\
sqlbrowser.exe and
create the exception of the file in Firewall, as delineated in
Step 3
.

7) Recreate Alias

It is getting quite common to create alias of SQL Server and use it in application. This will ensure
that in future if any physical SQL
Server has to be moved, it will not be required to change any
code or connection string. You can simply create alias with the same name pointing to different
SQL Server and it will start working instantaneously. I have observed that a couple of times due
t
o internal error while recreating alias this error was fixed.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Native Client
10.0 Configuration >> Aliases

Delete the alias that is giving problem and recreate it with identical
parameters.



Message 3:



[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL

Server [233].

[SQL Native Client]Login timeout expired

[SQL
Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.




-
OR
-



HResult 0x
E9, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [233].

Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be c
aused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error: Microsoft SQL Native Client : Login timeout expired.



Note: the difference between Message 2 and Message 1 is “Could not open a connection to SQL
Serve
r
[233]
.”


error state.



You might specify the server name as FQDN/127.0.0.1/ IP Address and NP was disabled on the
server. To resolve this, first way is to replace server name as the machine name or “.” or”(local)”
or “<machinename>” and you should be a
ble to connect as long as server listening on Shared
Memory; second way is to enable named pipe from sql configuration manager and restart server.



Message 4:



[SQL Native Client]Named Pipes Provider: No process is on the other end of the pipe.

[SQL Nati
ve Client]Communication link failure

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allo
w remote connections.



-
OR
-



HResult 0xE9, Level 16, State 1

Named Pipes Provider: No process is on the other end of the pipe.

Error: Microsoft SQL Native Client : Communication link failure.

Error: Microsoft SQL Native Client : An error has occurred
while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections..



1) Local connection: You might specify the server nam
e as FQDN/127.0.0.1/ IP Address in the
connection string and speculate connection through Named Pipe provider. To resolve this, either
change server name to <machinename> as long as the server is listening on Shared Memory or
enabled NP.

2) Remote connecti
on: the server is not listening on Name Pipe. To resolve this, enable name
pipe on the remote server and restart the server.



Message 5:



[SQL Native Client]SQL Network Interfaces: Server doesn't support requested protocol
[xFFFFFFFF].

[SQL Native Client
]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote conne
ctions.



-
OR
-



HResult 0xFFFFFFFF, Level 16, State 1

SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].

Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the
server. When connecting
to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections..

Error: Microsoft SQL Native Client : Login timeout expired.



1)


Local connection: You might explicitly specify pr
otocol prefix “np:” and connect to a named
instance and NP was disabled.

2)


Remote connection: You might connect to remote named instance and remote server is not
listening on name pipe.

To resolve this, enable NP if you only want to use name pipe pro
tocol or you can remove “np:”
prefix to let connection over shared memory locally.



Message 6:



[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified
[0xFFFFFFFF].

[SQL Native Client]Login timeout expired

[SQL Native
Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remot the connections.



-
OR
-



HResult
0xFFFFFFFF, Level 16, State 1

SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this f
ailure may be caused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error: Microsoft SQL Native Client : Login timeout expired.



You might connect to local named instance and explicitly specify protocol prefix “
tcp:” or “np:”
in the connection string, however, SqlBrowser service was not running.

To resolve this, you should enable Sqlbrowser service on the server

1)


Use net start or go to sql configuration manager(SSCM), check whether sqlbrowser service is
ru
nning, if not, start it.

2)


You still need to make sure SqlBrowser is active. Go to SSCM, click properties of sqlbrowser
service
-
> Advanced
-
> Active “Yes” or “No”, if sqlbrowser is running but is not active, the
service would not serve you correct pi
pe name and Tcp port info on which your connection
depends.



Message 7:

Shared Memory provider error



HResult 0x2, Level 16, State 1

Shared Memory Provider: Could not open a connection to SQL Server [2].

Error: Microsoft SQL Native Client : An error has

occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections..

Error: Microsoft SQL Native Client : Login ti
meout expired.



-
OR
-




[SQL Native Client]Shared Memory Provider: Could not open a connection to SQLServer [2].

[SQL Native Client]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.

The error indicate you speculated shared memory as connection protocol and server is not
listening on shared

memory, plus you probably specified “.”/”(local)”/<machinename> /localhost
as the server name in the connection string. To resolve this, enable shared memory protocol and
restart the server.



Message 8:



[SQL Native Client]SQL Network Interfaces: Canno
t open a Shared Memory connection to
a
remote SQL server [87].

[SQL Native Client]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused
by the fact that under the default
settings SQL Server does not allow remote connections.



-
OR
-



HResult 0x57, Level 16, State 1

SQL Network Interfaces: Cannot open a Shared Memory connection to a remote SQL server
[87].

Error: Microsoft SQL Native Clien
t : An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error: Microsoft SQL Native
Client : Login timeout expired.

The reason is same as the one of Message 6, just you might specify FQDN/127.0.0.1/IP Address
as server name in the connection string.



Message 9
: TCP specific



[SQL Native Client]TCP Provider: No connection could be made b
ecause the target machine
actively refused it.

[SQL Native Client]Login timeout expired

[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default
settings SQL Server does not allow remote connections.



-
OR
-



HResult 0x274D, Level 16, State 1

TCP Provider: No connection could be made because the target machine actively refused it.

Error: Microsoft SQL Native Client : An error has
occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not

allow remote connections..

Error: Microsoft SQL Native Client : Login
timeout expired.



The reason is server is not listening on TCP, probably TCP protocol was not enabled.



-
Follow messages are some special case

-




Message 10:




[SQL Native Client]Unable to complete login process due to delay in opening server
connection.



Reason:

1)


There are spaces after Instance name in the connection string eg. osql
/S”<machinename>
\
Instance


“ /E, to resolve this, you need to remove the trailing space.

2)


Connect through 127.0.01.

3)


Remote connection and WINS
was disabled on the client machine and you connect using
FQDN as server name. To resolve this, One way, turn on “File and Printer Sharing” and
explicitly use name pipe protocol. Another is enlarge the connect timeout to around 30 secondes.



Message 11:
-

Firewall specific



HResult 0x274C, Level 16, State 1

An error has occurred while establishing a connection to the server. When connectiong to SQL
Server 2005, this failure may be caused by the fact that under the default settings SQL Server
does not allow

remote connections.(provider:TCP Provider, errror:0
-
A connection attempt failed
because the connected party did not properly respond after a period of time, or established
connection failed because connected host has failed to respond.)



-
OR
-



Error: M
icrosoft SQL Native Client : An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections..

Erro
r: Microsoft SQL Native Client : Login timeout expired.



This is because connection blocked by firewall. To resolve this, take follow steps:

1)


Enable SqlBrowser, see the info in Message 4. Plus, add sqlbrowser.exe into Firewall
exception list:
HKEY_L
OCAL_MACHINE
\
SYSTEM
\
CurrentControlSet
\
Services
\
SharedAccess
\
Parameters
\
Fi
rewallPolicy
\
DomainProfile
\
AuthorizedApplications
\
List

2)


Add Tcp port to Firewall exception list. (eg, Name
-
1433:TCP, Value
-
1433:TCP:*:Enabled:Tcp 1433).

HKEY_LOCAL_MACHINE
\
SYSTE
M
\
CurrentControlSet
\
Services
\
SharedAccess
\
Parameters
\
Fi
rewallPolicy
\
DomainProfile
\
GloballyOpenPorts
\
List




LOGIN TO SERVER


ERRORS






You can set a new password for „sa“ account or you can create your own account for connection to
databáze.


Select account, go to properties and set new password.