Hi,
I have a pbm while connecting to the remote SQL server.
Recently we hired one win2003 based Dedicated server and installed SQl
server 2000. I have the sa password and the ip of the server, and when i
connect to this server from my local machine by configuring client n/w
utility, its giving me the error. like SQL server Does not exists ?
What shall i do ? i've disabled the firewall also, but not successful yet.
Also one more problem. The version i've installed is Enterprise Edition, and
will there be any problem if i uninstall it and reinstall the Standard
edition?
Thanking u in advance LaraHi
You should have no problems with un-installing Enterprise Edition and
re-installing Standard if you are not using any of the additional features
that it has. You may want to look at
http://support.microsoft.com/defaul...b;en-us;Q314546 for
transferring logins and dealing with Orphaned users if you have them. Make
sure that the new version is service packed and patched to the same level.
Backing up your database before un-installation will make sure that you have
a safe copy.
When you install the new system make sure that the correct protocols are
listed on the server's server network utilities. Check that you can ping the
server from your client and that the client also has the correct network
protocols. You may want to try SQLPing or SQLRecon to see if the server is
contactable.
John
"lara" <lara@.l.com> wrote in message
news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have a pbm while connecting to the remote SQL server.
> Recently we hired one win2003 based Dedicated server and installed SQl
> server 2000. I have the sa password and the ip of the server, and when i
> connect to this server from my local machine by configuring client n/w
> utility, its giving me the error. like SQL server Does not exists ?
> What shall i do ? i've disabled the firewall also, but not successful yet.
> Also one more problem. The version i've installed is Enterprise Edition,
> and
> will there be any problem if i uninstall it and reinstall the Standard
> edition?
>
> Thanking u in advance Lara
>|||I missed out the link for SQLPing and SQLRecon!
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hi
> You should have no problems with un-installing Enterprise Edition and
> re-installing Standard if you are not using any of the additional features
> that it has. You may want to look at
> http://support.microsoft.com/defaul...b;en-us;Q314546 for
> transferring logins and dealing with Orphaned users if you have them. Make
> sure that the new version is service packed and patched to the same level.
> Backing up your database before un-installation will make sure that you
> have a safe copy.
> When you install the new system make sure that the correct protocols are
> listed on the server's server network utilities. Check that you can ping
> the server from your client and that the client also has the correct
> network protocols. You may want to try SQLPing or SQLRecon to see if the
> server is contactable.
> John
>
> "lara" <lara@.l.com> wrote in message
> news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
>|||Thanks John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:eNJEsvqZFHA.3572@.TK2MSFTNGP12.phx.gbl...
> I missed out the link for SQLPing and SQLRecon!
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
> John
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
features
Make
level.
i
Edition,
>
Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts
Friday, March 23, 2012
Friday, March 9, 2012
Password protected Access 2000 DB
Hi everyone,
I'm having a problem connecting to my Access 2000 DB from VB.net 2003. The DB has an password protection, but no username/password protection. So, no .mdw files are used, only the DB own Jet password. At desing-mode, when connecting to DB first time, I'm asked the username (blanc) password (blanc) and the Jet database password ('myPass'). Everything works just fine until when I try to debug the program. Database login dialogbox appears and asks for username and password, but no Jet database password... So, I'm unable to connect. PLEASE help me on this one, because I starting to lose my mind while trying to find the answer. Thx in advance.
Jari@.FinlandPlease help. I'm desperate.|||I'm STILL strugging with this problem. Somebody, please help me. I've tried every solution presented on this forum (and every other that I was able to find) but the problem still exists. I managed to change the db path, userID and password at runtime, but can't find a way to enter the DB password... If I remove the password from DB everything works just fine. Even with normal logon information (userID & password). The TableLogOnInfo class doesn't give the option for DB password, only the UserID and password. The ConnectionInfo class has a password-option but I'm not sure is this for the DB password or what? And how should I use this class? I'll paste some code for you to see.
Dim oCRTab As New CrystalDecisions.Shared.TableLogOnInfo
Dim oCRConn As New CrystalDecisions.Shared.ConnectionInfo
Dim tab As Table
Dim report As New MyReport
tab = report .Database.Tables("MyTable")
oCRConn.Password = "TheDBPass"
oCRTab.ConnectionInfo = oCRConn
oCRTab.ConnectionInfo.ServerName = "c:\dbTest\db1.mdb"
oCRTab.TableName = "MyTable"
tab.ApplyLogOnInfo(oCRTab)
And later I bind the report to the CRViewer and it still asks for the login information...|||Yep, talking to myself again. Found out the solution to the problem: there isn't any... I received a post from businessobjects and found out this:
====================
NOTE:
You cannot set a database level password when
using Crystal Reports for Visual Studio .NET 2002 or
2003.
====================
So back to square one. I quess I'll have to find some other way to do my reports.
antijape .......boycottin CR since 2005.......
I'm having a problem connecting to my Access 2000 DB from VB.net 2003. The DB has an password protection, but no username/password protection. So, no .mdw files are used, only the DB own Jet password. At desing-mode, when connecting to DB first time, I'm asked the username (blanc) password (blanc) and the Jet database password ('myPass'). Everything works just fine until when I try to debug the program. Database login dialogbox appears and asks for username and password, but no Jet database password... So, I'm unable to connect. PLEASE help me on this one, because I starting to lose my mind while trying to find the answer. Thx in advance.
Jari@.FinlandPlease help. I'm desperate.|||I'm STILL strugging with this problem. Somebody, please help me. I've tried every solution presented on this forum (and every other that I was able to find) but the problem still exists. I managed to change the db path, userID and password at runtime, but can't find a way to enter the DB password... If I remove the password from DB everything works just fine. Even with normal logon information (userID & password). The TableLogOnInfo class doesn't give the option for DB password, only the UserID and password. The ConnectionInfo class has a password-option but I'm not sure is this for the DB password or what? And how should I use this class? I'll paste some code for you to see.
Dim oCRTab As New CrystalDecisions.Shared.TableLogOnInfo
Dim oCRConn As New CrystalDecisions.Shared.ConnectionInfo
Dim tab As Table
Dim report As New MyReport
tab = report .Database.Tables("MyTable")
oCRConn.Password = "TheDBPass"
oCRTab.ConnectionInfo = oCRConn
oCRTab.ConnectionInfo.ServerName = "c:\dbTest\db1.mdb"
oCRTab.TableName = "MyTable"
tab.ApplyLogOnInfo(oCRTab)
And later I bind the report to the CRViewer and it still asks for the login information...|||Yep, talking to myself again. Found out the solution to the problem: there isn't any... I received a post from businessobjects and found out this:
====================
NOTE:
You cannot set a database level password when
using Crystal Reports for Visual Studio .NET 2002 or
2003.
====================
So back to square one. I quess I'll have to find some other way to do my reports.
antijape .......boycottin CR since 2005.......
password problem
We have a problem with JDBC, clients on linux, connecting unless the password
is entered in lowercase.
Anyone got any ideas or heard of this before?
All was working fine until last week. We applied a instcat.sql upgrade to
our master database (from Microsoft suggestion for linked server connectivity
problem). After that upgrade, the only way we could connect is to set the
password in lower case and send the password in lowercase. On machines where
this wasn't applied, the case of the password doesn't matter.
Mark DeWaard wrote:
> We have a problem with JDBC, clients on linux, connecting unless the password
> is entered in lowercase.
> Anyone got any ideas or heard of this before?
> All was working fine until last week. We applied a instcat.sql upgrade to
> our master database (from Microsoft suggestion for linked server connectivity
> problem). After that upgrade, the only way we could connect is to set the
> password in lower case and send the password in lowercase. On machines where
> this wasn't applied, the case of the password doesn't matter.
Hi. It's clearly a DBMS upgrade issue. The driver just sends the password you
give it.
Joe Weinstein at BEA
>
is entered in lowercase.
Anyone got any ideas or heard of this before?
All was working fine until last week. We applied a instcat.sql upgrade to
our master database (from Microsoft suggestion for linked server connectivity
problem). After that upgrade, the only way we could connect is to set the
password in lower case and send the password in lowercase. On machines where
this wasn't applied, the case of the password doesn't matter.
Mark DeWaard wrote:
> We have a problem with JDBC, clients on linux, connecting unless the password
> is entered in lowercase.
> Anyone got any ideas or heard of this before?
> All was working fine until last week. We applied a instcat.sql upgrade to
> our master database (from Microsoft suggestion for linked server connectivity
> problem). After that upgrade, the only way we could connect is to set the
> password in lower case and send the password in lowercase. On machines where
> this wasn't applied, the case of the password doesn't matter.
Hi. It's clearly a DBMS upgrade issue. The driver just sends the password you
give it.
Joe Weinstein at BEA
>
Subscribe to:
Posts (Atom)