Showing posts with label vista. Show all posts
Showing posts with label vista. Show all posts

Wednesday, March 7, 2012

Cant create new database / CREATE DATABASE permission denied in database master (error 262

I am using SQL express and Visual web developer on windows Vista.

When I try to create a new database the following message appears.

CREATE DATABASE permission denied in database master (error 262)

I log on to my computer as an administrator.

Help appreciated

Prontonet

How do you login to sql server? Do you use sql authentication? If so, check the account you login with has appropriate permissions. Or are you using windows authentication?

|||

Can you login to database engine and read data anyway??

You need "CREATE DATABASE" permission to create new database. However, to make things easier, i would suggest you use sys_admin permission over your database.Open sql express and click "security"-->Logins, see if your login name is listed there. Rigth click your user name and select "properties", click "server roles" or "User Mappings" to see which role has been assigned to your account. If you are not a sys_admin/db_owner role, login agin using a dbo account(if you have one) and assign you account a sys_admin/dbo permission.

Hope my suggestion helps

Thursday, February 16, 2012

Can't connect to SQL 2005 in Vista

Hi. I hope someone can give me some ideas.
I have a SQL 2005 dev installed in my Vista and I tried to register it from
my Win 2003 server which also has SQL 2005. I get a time out message, it
seems the server cannot connect to my vista sql server. I already set my
vista sql server remote connection and restarted. Any idea? I don't have
issue to connect my server SQL from my vista. Is it something to do with
vista?
Thanks
KLWhat does "set my vista sql server remote connection" mean? Did you use the
surface area configuration tool to ensure that outside connections via
TCP/IP would be enabled? Also, is it a named instance or a default
instance? Are you using the correct instance name while trying to register
from Windows Server 2003? Are you inside a domain or a workgroup? Is it
possible that Windows firewall (or hardware firewall(s), or a program like
ZoneAlarm etc.) is blocking you from connecting? Is SQL Server using the
default port (1433) or is it custom? Can you ping the Vista machine from
Windows Server 2003? If so, can you telnet to the Vista machine on port
1433?
Aaron Bertrand
SQL Server MVP
"KL" <KwanLoonLai@.msn.com> wrote in message
news:C5507C7F-DAAC-4102-A510-201C3C4E247F@.microsoft.com...
> Hi. I hope someone can give me some ideas.
> I have a SQL 2005 dev installed in my Vista and I tried to register it
> from my Win 2003 server which also has SQL 2005. I get a time out
> message, it seems the server cannot connect to my vista sql server. I
> already set my vista sql server remote connection and restarted. Any idea?
> I don't have issue to connect my server SQL from my vista. Is it something
> to do with vista?
> Thanks
> KL|||- I use surface area configuration to enbled the remote connection with
both TCP/IP and name pipes
- It is a default instance
- Yes I use correct instance name to register the server, in this case I
use my computer name
- This is within a domain
- There is no third party firewall program running in my Vista, and I do
suspect vista built in firewall may block it, anyway I can find out ? I read
an article from
http://support.microsoft.com/defaul...kb;EN-US;914277 I follow
the step and add the sqlbrowser to exception list. still not working.
- I don't think I change any port when I installed sql server, if 1433 is
default it should be it
- I cant telnet to my vista with port 1433, but ping is fine
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:ORzmx630HHA.4184@.TK2MSFTNGP06.phx.gbl...
> What does "set my vista sql server remote connection" mean? Did you use
> the surface area configuration tool to ensure that outside connections via
> TCP/IP would be enabled? Also, is it a named instance or a default
> instance? Are you using the correct instance name while trying to
> register from Windows Server 2003? Are you inside a domain or a
> workgroup? Is it possible that Windows firewall (or hardware firewall(s),
> or a program like ZoneAlarm etc.) is blocking you from connecting? Is SQL
> Server using the default port (1433) or is it custom? Can you ping the
> Vista machine from Windows Server 2003? If so, can you telnet to the
> Vista machine on port 1433?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "KL" <KwanLoonLai@.msn.com> wrote in message
> news:C5507C7F-DAAC-4102-A510-201C3C4E247F@.microsoft.com...
>|||> - I cant telnet to my vista with port 1433, but ping is fine
Sounds to me like 1433 is blocked. It may be Windows firewall... you will
have to go into the config and make sure SQL (port 1433) is allowed at least
from the Windows Server 2003 IP.
A|||Thanks. It works after I put port 1433 in vista firewall exception.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:OAix3d40HHA.536@.TK2MSFTNGP06.phx.gbl...
> Sounds to me like 1433 is blocked. It may be Windows firewall... you will
> have to go into the config and make sure SQL (port 1433) is allowed at
> least from the Windows Server 2003 IP.
> A
>

Can't connect to SQL 2005 in Vista

Hi. I hope someone can give me some ideas.
I have a SQL 2005 dev installed in my Vista and I tried to register it from
my Win 2003 server which also has SQL 2005. I get a time out message, it
seems the server cannot connect to my vista sql server. I already set my
vista sql server remote connection and restarted. Any idea? I don't have
issue to connect my server SQL from my vista. Is it something to do with
vista?
Thanks
KL
What does "set my vista sql server remote connection" mean? Did you use the
surface area configuration tool to ensure that outside connections via
TCP/IP would be enabled? Also, is it a named instance or a default
instance? Are you using the correct instance name while trying to register
from Windows Server 2003? Are you inside a domain or a workgroup? Is it
possible that Windows firewall (or hardware firewall(s), or a program like
ZoneAlarm etc.) is blocking you from connecting? Is SQL Server using the
default port (1433) or is it custom? Can you ping the Vista machine from
Windows Server 2003? If so, can you telnet to the Vista machine on port
1433?
Aaron Bertrand
SQL Server MVP
"KL" <KwanLoonLai@.msn.com> wrote in message
news:C5507C7F-DAAC-4102-A510-201C3C4E247F@.microsoft.com...
> Hi. I hope someone can give me some ideas.
> I have a SQL 2005 dev installed in my Vista and I tried to register it
> from my Win 2003 server which also has SQL 2005. I get a time out
> message, it seems the server cannot connect to my vista sql server. I
> already set my vista sql server remote connection and restarted. Any idea?
> I don't have issue to connect my server SQL from my vista. Is it something
> to do with vista?
> Thanks
> KL

Can't connect to SQL 2005 in Vista

Hi. I hope someone can give me some ideas.
I have a SQL 2005 dev installed in my Vista and I tried to register it from
my Win 2003 server which also has SQL 2005. I get a time out message, it
seems the server cannot connect to my vista sql server. I already set my
vista sql server remote connection and restarted. Any idea? I don't have
issue to connect my server SQL from my vista. Is it something to do with
vista?
Thanks
KLWhat does "set my vista sql server remote connection" mean? Did you use the
surface area configuration tool to ensure that outside connections via
TCP/IP would be enabled? Also, is it a named instance or a default
instance? Are you using the correct instance name while trying to register
from Windows Server 2003? Are you inside a domain or a workgroup? Is it
possible that Windows firewall (or hardware firewall(s), or a program like
ZoneAlarm etc.) is blocking you from connecting? Is SQL Server using the
default port (1433) or is it custom? Can you ping the Vista machine from
Windows Server 2003? If so, can you telnet to the Vista machine on port
1433?
--
Aaron Bertrand
SQL Server MVP
"KL" <KwanLoonLai@.msn.com> wrote in message
news:C5507C7F-DAAC-4102-A510-201C3C4E247F@.microsoft.com...
> Hi. I hope someone can give me some ideas.
> I have a SQL 2005 dev installed in my Vista and I tried to register it
> from my Win 2003 server which also has SQL 2005. I get a time out
> message, it seems the server cannot connect to my vista sql server. I
> already set my vista sql server remote connection and restarted. Any idea?
> I don't have issue to connect my server SQL from my vista. Is it something
> to do with vista?
> Thanks
> KL|||- I use surface area configuration to enbled the remote connection with
both TCP/IP and name pipes
- It is a default instance
- Yes I use correct instance name to register the server, in this case I
use my computer name
- This is within a domain
- There is no third party firewall program running in my Vista, and I do
suspect vista built in firewall may block it, anyway I can find out ? I read
an article from
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 I follow
the step and add the sqlbrowser to exception list. still not working.
- I don't think I change any port when I installed sql server, if 1433 is
default it should be it
- I cant telnet to my vista with port 1433, but ping is fine
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ORzmx630HHA.4184@.TK2MSFTNGP06.phx.gbl...
> What does "set my vista sql server remote connection" mean? Did you use
> the surface area configuration tool to ensure that outside connections via
> TCP/IP would be enabled? Also, is it a named instance or a default
> instance? Are you using the correct instance name while trying to
> register from Windows Server 2003? Are you inside a domain or a
> workgroup? Is it possible that Windows firewall (or hardware firewall(s),
> or a program like ZoneAlarm etc.) is blocking you from connecting? Is SQL
> Server using the default port (1433) or is it custom? Can you ping the
> Vista machine from Windows Server 2003? If so, can you telnet to the
> Vista machine on port 1433?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "KL" <KwanLoonLai@.msn.com> wrote in message
> news:C5507C7F-DAAC-4102-A510-201C3C4E247F@.microsoft.com...
>> Hi. I hope someone can give me some ideas.
>> I have a SQL 2005 dev installed in my Vista and I tried to register it
>> from my Win 2003 server which also has SQL 2005. I get a time out
>> message, it seems the server cannot connect to my vista sql server. I
>> already set my vista sql server remote connection and restarted. Any
>> idea? I don't have issue to connect my server SQL from my vista. Is it
>> something to do with vista?
>> Thanks
>> KL
>|||> - I cant telnet to my vista with port 1433, but ping is fine
Sounds to me like 1433 is blocked. It may be Windows firewall... you will
have to go into the config and make sure SQL (port 1433) is allowed at least
from the Windows Server 2003 IP.
A|||Thanks. It works after I put port 1433 in vista firewall exception.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OAix3d40HHA.536@.TK2MSFTNGP06.phx.gbl...
>> - I cant telnet to my vista with port 1433, but ping is fine
> Sounds to me like 1433 is blocked. It may be Windows firewall... you will
> have to go into the config and make sure SQL (port 1433) is allowed at
> least from the Windows Server 2003 IP.
> A
>

Tuesday, February 14, 2012

Cant connect to remote server using SSMSE in Vista

Hi,

Sorry if this is the wrong forum.

I'm trying to connect to a remote server (on shared hosting) with Management Studio Express. I tried using it on Vista and it connects to the server and database perfectly. However, on Vista it gives the following error everytime:

TITLE: Connect to Server
----------

Cannot connect to sgc.gbdns.net.

----------
ADDITIONAL INFORMATION:

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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click:http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

----------
BUTTONS:

OK
----------

However, the host obviously has SQL server to allow remote connections as I'm able to connect from XP.

Both the XP and Vista PCs are running Avast free edition (the same builds) and both are running Windows firewall with management studio allowed through. Can anyone help?

I do not seam to have that problem on vista. I am running the sql express service pack 2 ctp(service pack 1 and earlier do not run on vista). Also when I start SSMSE I right click on the icon and select run as admin.|||

Thanks for your reply.

I don't habe the SP2 CTP installed. But isn't that for SQL Server rather than management studio? Plus, is your network set up as home, office or public location? I tried running as admin, running with compatibility mode set to XP SP2, nothing's working.

I also noticed that in windows firewall, management studio isn't listed as one of the programs by default. When trying to connect to the remote server, windows firewall doesn't ask me if I should allow the connection. I manually added management studio as an exception in windows firewall, but that didn't help. It seems the connection request isn't even going to windows firewall as it's not asking me to allow permission. Any ideas?

|||I also tried turning firewall and avast off. Didn't work.|||I could not even log into my local sql express on my machine until I loaded sql express with service pack 2.|||Thanks for the info. I guess I'mm lucky. I'll try SP2, but I still have doubts. I think our ISP may be blocking that port. Not sure, but I tried connecting from an XP of a friend who uses my ISP, and it failed. I'll check more possibilities tomorrow.|||

Hi,

The SQL Server 2005 might don't allow remote connection by default. You can try to enable it according to the following KB article.

http://support.microsoft.com/kb/914277/en-us

HTH. If this does not answer your question, please feel free to mark the post as Not Answered and we will look into it again. Thanks!

cant connect to remote db server using SQL 2005 in Vista

Hello
I use SQL 2005 - SQL Server Management Studio to connect to my hosting SQL Server to manage my database , its about 1 month which I have installed Vista and SQL 2005 its working fine in local , but today I just wanted to connect to my remote server and I got this error :

Cannot connect to <My server IP Address>

I thought its a server problem , but its not. I tested it by connecting using same SQL 2005 on a windows xp system , the problem is only in vista,
by the way its SQL 2005 SP2

what can I do to solve this probRight-click on the application and set the option to run in XP mode. Vista sucks.|||Hi,
SQL 2005 is default closed for remote connections.
On the local server, you should configure SQL Server instance and let the remote connections.
You can try the article http://www.kodyaz.com/content/SQLServerdoesnotallowremoteconnections.aspx for more detail

Eralper
http://www.kodyaz.com|||NO, you didn't get that,
The remote server which I am connecting to , is a SQL Server 2000 , and its working fine , I can easily connect to this server using SQL 2000 and 2005 through windows xp , the problem is that I can't connect to this server using SQL 2005 through windows Vista,
and I get "Cannot connect to <My server IP Address>"
I think this means its can't even connect to the server to check account details|||is there a firewall in vista that you need to configure?|||No , I have disabled firewall|||HI.
Make sure you can access the remote server over the network!
Check the networkprotocol you are using to connect to the remote sql.
Under the connection properties of management studio==> Network protocol; choose b/w namedpipes and tcp/ip (try switching between them).

Most likely the protocol being used is namedpipes which doesn't allow connection if the client machine is not within the domain remote server is running on or if namedpipes protocol is disabled on remote server.|||I checked each 3 connection protocol (Shared Memory , TCP/IP , namedpipes), but nothing, the same error

:(|||make sure the sql browser service is running on the remote sql server.|||I am sure that everything on the remote sql server is ok , because I easily connect to server with windows xp and sql 2005 the problem is only in windows vista and sql 2005|||somebody help me plz|||I wish we could, but this sounds like the sort of problem that we would have to be looking over your shoulder to spot. It would seem to be a problem with your operating systems, and not the database server, and thus may be outside the scope of our expertise.
Contact Microsquash, and when you do please tell them that blindman says Vista sucks.