Cannot create or modify tables in any database ("The parameter is incorrect.")

Using SQL Server 2005 and Microsoft SQL Server Management Studio, I connect using windows authentication. On any database I have created or attached (from a previous version of SQL Server), if I try to add a new table or modify an existing table, I get an error. A dialog pops up that says, "The parameter is incorrect." And I realy can't go any further.

I tried to remedy the problem by applying SP1 (x64) to the installation but I still get the same error.

Has anybody got a clue as to why I get this error? This is not SQL Server Express but the standard version of SQL Server. Fabulous software, I just can't get this to work on this new server. SQL Server Express is wonderful on our test machines but we need to get past this issue to fully utilize the server version.

Thanks for any help somebody can give me.

Please file a defect report on http://connect.microsoft.com/sqlserver. Defects reported on the Connect site go directly into our internal issue tracking system.

The error message pop-up should have a button/icon at bottom to show technical details. This includes the detailed exception message and the call stack. This can help us diagnose the problem. Be sure to include the version number of management studio and the engine (use menu Help | About to see the management studio version, and use this T-SQL to get the engine version: select @.@.version) and the call stack from the error dialog in the defect report.

One thing I would check is whether the database you've attached has a valid owner in the new server. If the database doesn't have an owner, you can give it one using the database properties dialog in management studio (connect to the server, right click on the database in Object Explorer, and select Properties. The owner can be set on the Files page.) or by issuing the "ALTER AUTHORIZATION ON DATABASE::{your db} TO {server principal}" statement in sqlcmd or a management studio query window.

You also need fairly high privileges to modify tables. Can you modify tables if you log in as a database owner?

Thanks,
Steve

Cannot connect using sql authentication in query analyzer

I just moved a database from one sql server to another. Both use Windows
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:

Cannot connect to SQL server with NT groups

Hi.
Have problems connecting to SQL server with NT group authentication.
Get error 4064: Error connecting to user default database.

There's no problems connecting with NT users og SQL users.

SQL2000 + Windows2000 both running latest service packs. All SP have been reinstalled.

The server suddenly stopped accepting NT group logins. It have been running for 1 year with no problems - 4 days ago it started generating this error.

Any ideas anyone?Talk to the network guys...something changed...

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?
Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>
|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>