Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts

Wednesday, March 21, 2012

MStudio Always "helps" me to connect to server

From database tree I want to open table trigger (I think this problem for all objects).

MStudio ALWAYS offer me to log on. Why?

I would like to open object from the SAME database, not other.

Can you provide more detail on exactly what you're trying to accomplish and the steps you're taking. Start with "I launch SSMS".

mssqlserverADhelper service terminated, Access Denied when trying to connect

This problem just started recently. This computer connected to the database
when it was first installed. All computer are new Compaq running Windows xp
pro.
This is a problem with MSDE. We are running MS Retail Management system.
One Point of Sale station won't connect to the server. I am running MSDE on
4 computers. One is the peer server it is named "serverxp" the one that
won't connect is "POS2". Other computers are POS1 and notebook. Below is
the case notes so far.
This one POS station is having a problem connection to the server database.
It has no problem connecting to the local database. What I see is on the SQL
Service Manager, When I select the network server "ServerXP" there is
nothing in the dropdown for services. When I select the local server then
three options are listed Dist. Tran, SQL Server and SQL Server agent.
This POS2 computer can connect to ServerXP and see shared folders etc. So I
haven't found any problem with the LAN or hardware.
Can you tell by this description what is wrong or what to try to do to fix
this?
Thanks
----
6/9/2004 1:28:00 PM CDT -- Allison Haaland
Steven,
I have a few more questions for you in order to further troubleshoot this
issue:
1. When you look at the SQL Server Service Manager and choose the "ServerXP"
option, does it say Not Connected at the bottom? yes
2. When you select the local server option in SQL Server Service Manager,
can you then connect to the database in Administrator? (You would choose
local as your server in Administrator as well.) yes
3. If you go to Start | Control | Administrative Tools | Services, do you
see your MSSQL and SQLAgent options there? If so, is the Status showing as
'Started'? If not, you should make sure that the Services are started if
you're trying to use them.
.MSSQLServer is started
MSSQLServerADhelper is set to manual and will not start "could not start
access denied"
4. Is there anything else that is different about this workstation from the
others? This might help us find out why it is not working, but all of the
others are. no
Thanks,
Allison
----
6/9/2004 3:51:00 PM CDT -- Steven
Allison:
More Info. An error in the System error log shows.
The mssqlserverADhelper service terminated with service specific error
3221225572 error 2270 refer to Knowledge base 314094. ID 7024
this is talking about the computer name. The name of this PC is POS2 it is
unique on this network.
----
6/9/2004 4:43:00 PM CDT -- Allison Haaland
Steven,
It looks like the error you are running into now is a network related issue
related to your computer name. I see that you have already referenced
Knowledge base article #314094 - have you tried the steps that it gives to
resolve this error? YES.
POS2 was working correctly at the time it was installed. No name have been
changed.
Can anyone with more experience working with SQL server give me some help
correcting this problem? Thank you.Hi Steve,
What error is generated with the connection fails?
Create an ODBC Test DSN and post the entire message here.
The ADHelper servers is not required for machines to connect to one
another. It's used to publish objects to Active Directory.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

mssqlserverADhelper service terminated, Access Denied when trying to connect

This problem just started recently. This computer connected to the database
when it was first installed. All computer are new Compaq running Windows xp
pro.
This is a problem with MSDE. We are running MS Retail Management system.
One Point of Sale station won't connect to the server. I am running MSDE on
4 computers. One is the peer server it is named "serverxp" the one that
won't connect is "POS2". Other computers are POS1 and notebook. Below is
the case notes so far.
This one POS station is having a problem connection to the server database.
It has no problem connecting to the local database. What I see is on the SQL
Service Manager, When I select the network server "ServerXP" there is
nothing in the dropdown for services. When I select the local server then
three options are listed Dist. Tran, SQL Server and SQL Server agent.
This POS2 computer can connect to ServerXP and see shared folders etc. So I
haven't found any problem with the LAN or hardware.
Can you tell by this description what is wrong or what to try to do to fix
this?
Thanks
6/9/2004 1:28:00 PM CDT -- Allison Haaland
Steven,
I have a few more questions for you in order to further troubleshoot this
issue:
1. When you look at the SQL Server Service Manager and choose the "ServerXP"
option, does it say Not Connected at the bottom? yes
2. When you select the local server option in SQL Server Service Manager,
can you then connect to the database in Administrator? (You would choose
local as your server in Administrator as well.) yes
3. If you go to Start | Control | Administrative Tools | Services, do you
see your MSSQL and SQLAgent options there? If so, is the Status showing as
'Started'? If not, you should make sure that the Services are started if
you're trying to use them.
..MSSQLServer is started
MSSQLServerADhelper is set to manual and will not start "could not start
access denied"
4. Is there anything else that is different about this workstation from the
others? This might help us find out why it is not working, but all of the
others are. no
Thanks,
Allison
6/9/2004 3:51:00 PM CDT -- Steven
Allison:
More Info. An error in the System error log shows.
The mssqlserverADhelper service terminated with service specific error
3221225572 error 2270 refer to Knowledge base 314094. ID 7024
this is talking about the computer name. The name of this PC is POS2 it is
unique on this network.
6/9/2004 4:43:00 PM CDT -- Allison Haaland
Steven,
It looks like the error you are running into now is a network related issue
related to your computer name. I see that you have already referenced
Knowledge base article #314094 - have you tried the steps that it gives to
resolve this error? YES.
POS2 was working correctly at the time it was installed. No name have been
changed.
Can anyone with more experience working with SQL server give me some help
correcting this problem? Thank you.
Hi Steve,
What error is generated with the connection fails?
Create an ODBC Test DSN and post the entire message here.
The ADHelper servers is not required for machines to connect to one
another. It's used to publish objects to Active Directory.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Wednesday, March 7, 2012

MSSQL with evc++ application

Hi all,
I am developing a software on Pocket PC. I just want to connect my application developed in eVC++ 4.0 with WinCE with a database on MSSQL. How it can be done?? Please help.

Quote:

Originally Posted by pw123

Hi all,
I am developing a software on Pocket PC. I just want to connect my application developed in eVC++ 4.0 with WinCE with a database on MSSQL. How it can be done?? Please help.


I don't think it is a right forum for this question.
Try this reference:
http://www.ondotnet.com/pub/a/dotnet/2003/01/06/sqlce20.html?page=last

Saturday, February 25, 2012

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech Znaniecki
Is SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegro ups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech ZnanieckiIs SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegroups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSSQL Server 2005 reported account locked out for user 'sa'

Greetings,

I receive an error message in event log when i try to connect to the Database Server using ODBC on a client machine. The database server is running on Windows 2003 Server Standard Edition and the client machine is Windows XP Professional. Following is the error message from the event log:

2147467259 - [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa' because the account is currently locked out. The system administrator can unlock it.

What causes the error to occur and how to resolve it?Appreciate for your assistence.

Thanks and regards,

Viknes

That error message means that the number of unsuccessful attempts to connect as the ‘sa’ account on your server and triggered the lockout policy on SQL Server 2005 for this account.

I would recommend verifying the logs and trying to find out the reason why the account was locked out. It is possible that one of your applications is using an outdated password and it needs to be fixed, but it may also be possible it was an automated attack trying to guess the SA password.

The following links will hopefully help you to resolve your problem, but if you have any further question or if the documentation is not clear enough, please let us know:

· Password Policy (http://msdn2.microsoft.com/en-us/library/ms161959.aspx)

· Alter Login (TSQL) (http://msdn2.microsoft.com/en-us/library/ms189828.aspx)

· Changing password programmatically (http://msdn2.microsoft.com/en-us/library/ms131024.aspx)

-Raul Garcia

SDE/T

SQL Server Engine

|||Also remember that SQL Server accounts can now use Windows Security policies on whiche SQL Server is running(Password complexity, password expiration, etc.) This only works for Windows Server 2003