Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Monday, March 26, 2012

error during installing SP3

Hi
I've got following error during installing SP3
by running this file Sql2kasp3.exe after successfully
installation sql 2ksp3.exe,
(SQL server 2000,server station)
"an error occurred during move data process : -145"
Thanks for any reply
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Are you running analysis services?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1kakxwshqligo@.msnews.microsoft.com...
> Hi
> I've got following error during installing SP3
> by running this file Sql2kasp3.exe after successfully
> installation sql 2ksp3.exe,
> (SQL server 2000,server station)
> "an error occurred during move data process : -145"
> Thanks for any reply
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/sql

error during installing SP3

Hi
I've got following error during installing SP3
by running this file Sql2kasp3.exe after successfully
installation sql 2ksp3.exe,
(SQL server 2000,server station)
"an error occurred during move data process : -145"
Thanks for any reply
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Are you running analysis services?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1kakxwshqligo@.msnews.microsoft.com...
quote:

> Hi
> I've got following error during installing SP3
> by running this file Sql2kasp3.exe after successfully
> installation sql 2ksp3.exe,
> (SQL server 2000,server station)
> "an error occurred during move data process : -145"
> Thanks for any reply
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

error during install SP3

Hi
I've SQL server 2000 on server station and wanted
to install SP3,at first installation of sql2ksp3.exe
was completed successfully,and following error appearred
on running sql2kasp3.exe:
"An error occurred during move data process : -145"
why ?
what's wrong?
any help would be greatly appreciated.
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Hi
Sql2kasp3.exe Updates Analysis Services is this actually installed?
John
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1linpoqhqligo@.msnews.microsoft.com...
quote:

> Hi
> I've SQL server 2000 on server station and wanted
> to install SP3,at first installation of sql2ksp3.exe
> was completed successfully,and following error appearred
> on running sql2kasp3.exe:
> "An error occurred during move data process : -145"
> why ?
> what's wrong?
> any help would be greatly appreciated.
> --
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
|||no ,I didn't install completely
an error casued to exit it,
On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
<jbellnewsposts@.hotmail.com> wrote:
quote:

> Hi
> Sql2kasp3.exe Updates Analysis Services is this actually installed?
> John
> "RM" <m_r1824@.yahoo.co.uk> wrote in message
> news:opr1linpoqhqligo@.msnews.microsoft.com...
>

Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||Hi
Sql2kasp3.exe will update your existing install of Analysis services,
you need Analysis services to already be installed and working before
applying this patch.
John
RM <m_r1824@.yahoo.co.uk> wrote in message news:<opr1nbozoghqligo@.msnews.microsoft.com>...[QUOTE][c
olor=darkred]
> no ,I didn't install completely
> an error casued to exit it,
> On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
> <jbellnewsposts@.hotmail.com> wrote:
>

error during install SP3

Hi
I've SQL server 2000 on server station and wanted
to install SP3,at first installation of sql2ksp3.exe
was completed successfully,and following error appearred
on running sql2kasp3.exe:
"An error occurred during move data process : -145"
why ?
what's wrong?
any help would be greatly appreciated.
--
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Hi
Sql2kasp3.exe Updates Analysis Services is this actually installed?
John
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1linpoqhqligo@.msnews.microsoft.com...
> Hi
> I've SQL server 2000 on server station and wanted
> to install SP3,at first installation of sql2ksp3.exe
> was completed successfully,and following error appearred
> on running sql2kasp3.exe:
> "An error occurred during move data process : -145"
> why ?
> what's wrong?
> any help would be greatly appreciated.
> --
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||no ,I didn't install completely
an error casued to exit it,
On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
<jbellnewsposts@.hotmail.com> wrote:
> Hi
> Sql2kasp3.exe Updates Analysis Services is this actually installed?
> John
> "RM" <m_r1824@.yahoo.co.uk> wrote in message
> news:opr1linpoqhqligo@.msnews.microsoft.com...
>> Hi
>> I've SQL server 2000 on server station and wanted
>> to install SP3,at first installation of sql2ksp3.exe
>> was completed successfully,and following error appearred
>> on running sql2kasp3.exe:
>> "An error occurred during move data process : -145"
>> why ?
>> what's wrong?
>> any help would be greatly appreciated.
>> --
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||Hi
Sql2kasp3.exe will update your existing install of Analysis services,
you need Analysis services to already be installed and working before
applying this patch.
John
RM <m_r1824@.yahoo.co.uk> wrote in message news:<opr1nbozoghqligo@.msnews.microsoft.com>...
> no ,I didn't install completely
> an error casued to exit it,
> On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
> <jbellnewsposts@.hotmail.com> wrote:
> > Hi
> >
> > Sql2kasp3.exe Updates Analysis Services is this actually installed?
> >
> > John
> >
> > "RM" <m_r1824@.yahoo.co.uk> wrote in message
> > news:opr1linpoqhqligo@.msnews.microsoft.com...
> >> Hi
> >>
> >> I've SQL server 2000 on server station and wanted
> >> to install SP3,at first installation of sql2ksp3.exe
> >> was completed successfully,and following error appearred
> >> on running sql2kasp3.exe:
> >>
> >> "An error occurred during move data process : -145"
> >>
> >> why ?
> >> what's wrong?
> >> any help would be greatly appreciated.
> >>
> >> --
> >>
> >> --
> >> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
> >
> >

Sunday, March 11, 2012

error converting the char value BUT IT IS A CHAR ALREADY

SQL Server 2000 SP3a
Access 2000 SP3 (using adp)
Im going mildly loopy, hopefully someone can aid my sanity.
Table in SQL Server had a column (column_a tinyint), data contained is just
ones and zeros. In Enterprise Manager I changed the data type of column_a t
o
char(1), so that I could then go and replace the ones and zeros with 'Y' and
'N'
When I try and change one of the values, through either Access or Enterprise
Manager, it errors with:
"Syntax error converting the char value 'Y' to a column of data type int"
I don't understand, I've changed the columns data type from tinyint to
char(1), so surely these updates should work. Whats the problem with this?
I've taken the db offline, I've even tried booting the server (clutching at
straws). What might not have been updated correctly?
Any suggestions would be great!
Its these stupid things which should be a two second job, but end up taking
me hours. And yes, if I'd got it right in the first instance, then this
wouldn't have been a problem :)
Thanks for any replies.I would have thought that the logical way to proceed would have been:
1. Add a field of Char(1) to the table with a different name than the source
field
2. Update this new field to 'Y' and 'N' based on the source field's values
3. Remove the source field
4. Rename the new field to that of the source field.
I'm surprised that SQLEM would even let you change a TinyInt to a Char in th
e
first place. If it did, what values are in that field?
Thomas|||1- Be sure it has been changed. See deifnition using view
information_schema.columns
2 - Try doing the update from query analyzer.
update table1
set colB = substring('NY', cast(colB as int) + 1, 1)
AMB
"Steve'o" wrote:

> SQL Server 2000 SP3a
> Access 2000 SP3 (using adp)
> Im going mildly loopy, hopefully someone can aid my sanity.
> Table in SQL Server had a column (column_a tinyint), data contained is jus
t
> ones and zeros. In Enterprise Manager I changed the data type of column_a
to
> char(1), so that I could then go and replace the ones and zeros with 'Y' a
nd
> 'N'
> When I try and change one of the values, through either Access or Enterpri
se
> Manager, it errors with:
> "Syntax error converting the char value 'Y' to a column of data type int"
> I don't understand, I've changed the columns data type from tinyint to
> char(1), so surely these updates should work. Whats the problem with this
?
> I've taken the db offline, I've even tried booting the server (clutching a
t
> straws). What might not have been updated correctly?
> Any suggestions would be great!
> Its these stupid things which should be a two second job, but end up takin
g
> me hours. And yes, if I'd got it right in the first instance, then this
> wouldn't have been a problem :)
> Thanks for any replies.|||> Table in SQL Server had a column (column_a tinyint), data contained is
just
> ones and zeros. In Enterprise Manager I changed the data type of column_a
to
> char(1), so that I could then go and replace the ones and zeros with 'Y'
and
> 'N'
> When I try and change one of the values, through either Access or
Enterprise
> Manager, it errors with:
> "Syntax error converting the char value 'Y' to a column of data type int"
While I don't have any obvious suggestion to help with EM, Access has a bit
of odd behavior. If you "Link" a SQL Server table into an Access database,
Access "remembers" the schema of the table, so that if you then do something
to the schema of the SQL Server table, Access is not aware of the change.
The workaround that I have used is to delete the linked table in Access and
re-link to it. I also like to rename it to get rid of the stupid "dbo_"
prefix that Access adds.
--
Peace & happy computing,
Mike Labosh, MCSD
"Escriba coda ergo sum." -- vbSensei|||Wow, several replies, thanks.
Thomas
I did not mention this, but there are several triggers and check consraints,
basically several dependencies to the column_a. I did try creating a new
column_a_new (char1), then tried renaming column_a to column_a_old, but it
wasn't having it because of the dependencies. In an Access .mdb you can get
away with this, but sql server appears a bit more rigid in this type of
workaround.
Alejandro
I made the changes a few days ago (I have been trying to fix it in that
time) and the server and cient machine have been booted a few times.
I double checked information_scheme.columns, great suggestion thanks, and
got this which seems a little odd to me as I set it to char(1), which is doe
s
display as in Access and EM.
ORDINAL_POSITION
16
COLUMN_DEFAULT
('N')
IS_NULLABLE
No
DATA_TYPE
nvarchar
CHARACTER_MAXIMUM_LENGTH
50
CHARACTER_OCTET_LENGTH
100
QA gives the same error when doing an update set
Server: Msg 245, Level 16, State 1, Line 1
Syntax error converting the varchar value 'N' to a column of data type int.
Mike
Yeah, there are lots of little tricks which need to be remembered with
Access (especially 2000) and SQL Server :)
I am using an .adp which is a bit different to an .mdb with linked tables,
but F5 is definitely your freind :)
I have booted the client and server, as I've been messing around for a few
days, so it should be refreshed. And it occurs in EM+QA too.
Thanks to all replies, its sounding horribly like Im going to have to drop
all dependencies, then re-create them after deleting the old column and
adding a new one. Maybe use EM to create a .sql script of the objects
including drop_all first, then alter the script to use char, then run
it....What a hassle, certainly won't make this mistake again, hopefully ;)
PS, is it better to reply to each individual post, or top post with a msg
like this, or bottom post with a msg like this ie including replies to
several people?
Or does it not really matter?
"Mike Labosh" wrote:

> just
> to
> and
> Enterprise
> While I don't have any obvious suggestion to help with EM, Access has a bi
t
> of odd behavior. If you "Link" a SQL Server table into an Access database
,
> Access "remembers" the schema of the table, so that if you then do somethi
ng
> to the schema of the SQL Server table, Access is not aware of the change.
> The workaround that I have used is to delete the linked table in Access an
d
> re-link to it. I also like to rename it to get rid of the stupid "dbo_"
> prefix that Access adds.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "Escriba coda ergo sum." -- vbSensei
>
>|||> I did not mention this, but there are several triggers and check consraints,d">
> basically several dependencies to the column_a. I did try creating a new
> column_a_new (char1), then tried renaming column_a to column_a_old, but it
> wasn't having it because of the dependencies. In an Access .mdb you can g
et
> away with this, but sql server appears a bit more rigid in this type of
> workaround.
The obvious answer is to drop the triggers and check constraints before you
run
through the steps I suggested and then re-add the triggers and check constra
ints
afterwards. It's not that difficult. You can use the query analyzer to scrip
t
the creation of the appropriate triggers and check constraints as well as sc
ript
the drop scripts for these. Besides, it is likely that these triggers and ch
eck
constraints need to change anyway.

> PS, is it better to reply to each individual post, or top post with a msg
> like this, or bottom post with a msg like this ie including replies to
> several people?
> Or does it not really matter?
Doubt it matters much.
Thomas|||On Mon, 11 Apr 2005 10:00:01 -0700, Steve'o wrote:

>PS, is it better to reply to each individual post, or top post with a msg
>like this, or bottom post with a msg like this ie including replies to
>several people?
>Or does it not really matter?
Hi Steve'o,
Trying to start a flame-war? <grin>
Top-posting vs bottom-posting can turn into a heated debate. I believe
that most Usenet regulars prefer bottom-posting or inline reply (quote,
reply, quote, reply, ...). However, MS Outlook defaults to top-posting,
as does (if I recall correctly) MS' internet portal to the MS related
groups.
Since this group is about an MS product, a relatively large number of
users use Outlook or MS' internet portal for access. As a result, you'll
see lots of top-posting here.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

error converting data type int to tiny int

While trying to create a new database maintenance plan in SQL 2000 sp3, I'm
receiving the error "error converting data type int to tiny int". No matter
what I select in the plan, the same error appears. I have a bare bone backu
p
of 1 database to disk, and receive the error. I've not been able to find
anything, except for a few people having the same sort of problem, who are
running more than 1 instance of sql on their server, as is the case with me.
thank you,I don't know why the error but if you are simply doing a backup why not
create a scheduled job yourself and forget about the Maintenance plan?
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
> While trying to create a new database maintenance plan in SQL 2000 sp3,
> I'm
> receiving the error "error converting data type int to tiny int". No
> matter
> what I select in the plan, the same error appears. I have a bare bone
> backup
> of 1 database to disk, and receive the error. I've not been able to find
> anything, except for a few people having the same sort of problem, who are
> running more than 1 instance of sql on their server, as is the case with
> me.
> thank you,
>|||Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or from
Management Backup?
"Andrew J. Kelly" wrote:

> I don't know why the error but if you are simply doing a backup why not
> create a scheduled job yourself and forget about the Maintenance plan?
> --
> Andrew J. Kelly SQL MVP
>
> "Bill" <Bill@.discussions.microsoft.com> wrote in message
> news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
>
>|||Yes under Management, SQL agent, Jobs, you can right click and add a new
job. Then in the Jobstep you place the TSQL BACKUP DATABASE xxx command.
You can set a schedule as you see fit.
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:4F8344E5-0A46-499F-9A2C-6B263EB9F23C@.microsoft.com...[vbcol=seagreen]
> Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or
> from
> Management Backup?
>
> "Andrew J. Kelly" wrote:
>

error converting data type int to tiny int

While trying to create a new database maintenance plan in SQL 2000 sp3, I'm
receiving the error "error converting data type int to tiny int". No matter
what I select in the plan, the same error appears. I have a bare bone backup
of 1 database to disk, and receive the error. I've not been able to find
anything, except for a few people having the same sort of problem, who are
running more than 1 instance of sql on their server, as is the case with me.
thank you,I don't know why the error but if you are simply doing a backup why not
create a scheduled job yourself and forget about the Maintenance plan?
--
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
> While trying to create a new database maintenance plan in SQL 2000 sp3,
> I'm
> receiving the error "error converting data type int to tiny int". No
> matter
> what I select in the plan, the same error appears. I have a bare bone
> backup
> of 1 database to disk, and receive the error. I've not been able to find
> anything, except for a few people having the same sort of problem, who are
> running more than 1 instance of sql on their server, as is the case with
> me.
> thank you,
>|||Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or from
Management Backup?
"Andrew J. Kelly" wrote:
> I don't know why the error but if you are simply doing a backup why not
> create a scheduled job yourself and forget about the Maintenance plan?
> --
> Andrew J. Kelly SQL MVP
>
> "Bill" <Bill@.discussions.microsoft.com> wrote in message
> news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
> > While trying to create a new database maintenance plan in SQL 2000 sp3,
> > I'm
> > receiving the error "error converting data type int to tiny int". No
> > matter
> > what I select in the plan, the same error appears. I have a bare bone
> > backup
> > of 1 database to disk, and receive the error. I've not been able to find
> > anything, except for a few people having the same sort of problem, who are
> > running more than 1 instance of sql on their server, as is the case with
> > me.
> >
> > thank you,
> >
>
>|||Yes under Management, SQL agent, Jobs, you can right click and add a new
job. Then in the Jobstep you place the TSQL BACKUP DATABASE xxx command.
You can set a schedule as you see fit.
--
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:4F8344E5-0A46-499F-9A2C-6B263EB9F23C@.microsoft.com...
> Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or
> from
> Management Backup?
>
> "Andrew J. Kelly" wrote:
>> I don't know why the error but if you are simply doing a backup why not
>> create a scheduled job yourself and forget about the Maintenance plan?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Bill" <Bill@.discussions.microsoft.com> wrote in message
>> news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
>> > While trying to create a new database maintenance plan in SQL 2000 sp3,
>> > I'm
>> > receiving the error "error converting data type int to tiny int". No
>> > matter
>> > what I select in the plan, the same error appears. I have a bare bone
>> > backup
>> > of 1 database to disk, and receive the error. I've not been able to
>> > find
>> > anything, except for a few people having the same sort of problem, who
>> > are
>> > running more than 1 instance of sql on their server, as is the case
>> > with
>> > me.
>> >
>> > thank you,
>> >
>>

error converting data type int to tiny int

While trying to create a new database maintenance plan in SQL 2000 sp3, I'm
receiving the error "error converting data type int to tiny int". No matter
what I select in the plan, the same error appears. I have a bare bone backup
of 1 database to disk, and receive the error. I've not been able to find
anything, except for a few people having the same sort of problem, who are
running more than 1 instance of sql on their server, as is the case with me.
thank you,
I don't know why the error but if you are simply doing a backup why not
create a scheduled job yourself and forget about the Maintenance plan?
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
> While trying to create a new database maintenance plan in SQL 2000 sp3,
> I'm
> receiving the error "error converting data type int to tiny int". No
> matter
> what I select in the plan, the same error appears. I have a bare bone
> backup
> of 1 database to disk, and receive the error. I've not been able to find
> anything, except for a few people having the same sort of problem, who are
> running more than 1 instance of sql on their server, as is the case with
> me.
> thank you,
>
|||Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or from
Management Backup?
"Andrew J. Kelly" wrote:

> I don't know why the error but if you are simply doing a backup why not
> create a scheduled job yourself and forget about the Maintenance plan?
> --
> Andrew J. Kelly SQL MVP
>
> "Bill" <Bill@.discussions.microsoft.com> wrote in message
> news:2F56B630-C272-4125-A5D0-08ADE9E284A8@.microsoft.com...
>
>
|||Yes under Management, SQL agent, Jobs, you can right click and add a new
job. Then in the Jobstep you place the TSQL BACKUP DATABASE xxx command.
You can set a schedule as you see fit.
Andrew J. Kelly SQL MVP
"Bill" <Bill@.discussions.microsoft.com> wrote in message
news:4F8344E5-0A46-499F-9A2C-6B263EB9F23C@.microsoft.com...[vbcol=seagreen]
> Do you mean use a T-SQL statement under Management, SQL agent, Jobs, or
> from
> Management Backup?
>
> "Andrew J. Kelly" wrote:

Friday, March 9, 2012

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
Thanks
Hi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>
|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
ThanksHi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Friday, February 24, 2012

Error changing SA password

I'm getting the following error when trying to change the
SA password for SQL Server2000 (SP3).
"Error 21776:[SQL_DMO]The name 'dbo' was not found in the
Users collection. If the name is a qualified name, use []
to separate various parts of the name, and try again"
I can't seem to connect under the old or the new
password. Any help would be appreciated.
Thanks
RonAre you a domain admin..? If so connect to SQL via Query Analyser using
Windows Authentication. Then issue the following :-
Examples
A. Change the password of a login without the former password
This example changes the password for the login Victoria to ok.
EXEC sp_password NULL, 'ok', 'Victoria'
--
HTH
Ryan Waight, MCDBA, MCSE
"Ron" <rgowdy@.phcs.com> wrote in message
news:18c201c38695$637b2610$a001280a@.phx.gbl...
> I'm getting the following error when trying to change the
> SA password for SQL Server2000 (SP3).
> "Error 21776:[SQL_DMO]The name 'dbo' was not found in the
> Users collection. If the name is a qualified name, use []
> to separate various parts of the name, and try again"
> I can't seem to connect under the old or the new
> password. Any help would be appreciated.
> Thanks
> Ron|||Just to add to Ryan's reply, you can change the password
with Query Analyzer but you will still have the issue of a
dbo being mapped to a non-existant login - that's what
causes the error. You should still update your databases
using sp_changedbowner so that they are owned by logins that
exist on the server.
-Sue
On Mon, 29 Sep 2003 07:24:27 -0700, "Ron" <rgowdy@.phcs.com>
wrote:
>I'm getting the following error when trying to change the
>SA password for SQL Server2000 (SP3).
>"Error 21776:[SQL_DMO]The name 'dbo' was not found in the
>Users collection. If the name is a qualified name, use []
>to separate various parts of the name, and try again"
>I can't seem to connect under the old or the new
>password. Any help would be appreciated.
>Thanks
>Ron|||I believe Sue is on the money here. See the link below
http://www.google.com/groups?selm=utApDPZeDHA.2080%40TK2MSFTNGP12.phx.gbl&oe=UTF-8&output=gplain
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Ron" <rgowdy@.phcs.com> wrote in message
news:18c201c38695$637b2610$a001280a@.phx.gbl...
> I'm getting the following error when trying to change the
> SA password for SQL Server2000 (SP3).
> "Error 21776:[SQL_DMO]The name 'dbo' was not found in the
> Users collection. If the name is a qualified name, use []
> to separate various parts of the name, and try again"
> I can't seem to connect under the old or the new
> password. Any help would be appreciated.
> Thanks
> Ron

Friday, February 17, 2012

error attaching db...

Hello,

I tried to attach my database (SQL Server 2000 w/ SP3) at work after taking it home to work on it and it gave me an error.

I tried to attaching my backup one as one (which use to work) and now does not. I treid to attach other DB's and they are fine.

The error message displayed on the screen is:

----
Microsoft SQL-DMO (ODBC SQLState:HY000)

X Error 3264
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 51
Process ID: 1004
----

The error message recorded in Event Viewer is:

------
Event ID: 17055

17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.

------

Any ideas what could have gone wrong? or is it simply a matter of reinstalling SQL server.

thanks,

JPCheck this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH|||Originally posted by Satya
Check this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH

Hey satya,

thanks for the heads up. I don't understand why it should be a SP issue because both of them are the same and it use to work before. Last week, I did the same... detach the DB, worked on it at home and rettached it back at work... no problem.

Oh well, such is life ... full of disappointments. I'll reintall the SP and see what happens. Maybe I'll do a windows update as well cuz we never know if it does affect anything else.

I'll report back should I get the problem fixed.

thanks,

JP|||Originally posted by globeuser
Hey satya,

thanks for the heads up. I don't understand why it should be a SP issue because both of them are the same and it use to work before. Last week, I did the same... detach the DB, worked on it at home and rettached it back at work... no problem.

Oh well, such is life ... full of disappointments. I'll reintall the SP and see what happens. Maybe I'll do a windows update as well cuz we never know if it does affect anything else.

I'll report back should I get the problem fixed.

thanks,

JP

Nope.. same error result. did not work. I've reapplied SP3 and unfortunately I'm still getting this error.

One factor though... I ftp'd down the DB instead of making a copy on the CD but I've downloaded them a number of times and still the same error appears.

any other ideas anyone?

kinda desperate ;-) Guess I'll have to reinstall?

JP|||Originally posted by Satya
Check this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH

Yup... looks like a reinstall is the only option because I am now getting another error message:

--------

Microsoft SQL-DMO (ODBC SQLState:42000)

X Error 1813: Cound not opne new database 'MyProject'. CREATE DATABASE is aborterd.
SQlDumpExceptionHandler: Process 51 genrated fatal exception c0000005 EXCEPTION_ACCESS_violation
Server is terminating this process.

--------

any other ideas?

JP|||Last resort to contact MS PSS for any fix on this EAV issues.|||Originally posted by Satya
Last resort to contact MS PSS for any fix on this EAV issues.

I had a hunch that it might just be as simple s this but I remembered that when I tried to detach it, it took some time because there were stilll some connections to it and I "forced it" to disconnect. It should not take that long because I have a very fast machine.

Lucky for me that the database was still there and I reattached it again first thing before any connections or apps have access to it.

The detachment is now clean and was able to attach it now to another machine.

The lesson learned is that the detach process was dirty or forced and all I had to do was to do it again before any other applications has a lock on it.

JP|||Thats fine, but before you detach make sure to run health checks and DBCC against the database to make sure its lively.|||Originally posted by Satya
Thats fine, but before you detach make sure to run health checks and DBCC against the database to make sure its lively.

Sorry, but how do you do that? I noticed that when I tried to run one of my stored procedures or view the properties in the DB, i get an error displayed...

And when I tried to delete the stored procedure to recreate it won't allow me to or can't delete it!

------
Microsoft SQL-DMO (ODBC SQLState:HY000)

X Error 605: Attempt to to fetch logical page (1:0) in database 'MyProject' belongs to object 'ALLOCATION', not to object 'syscomments'.
------

I am running ColdFusion 5 and this was what was displayed.

------
ODBC Error Code = S1000 (General error)

[Microsoft][ODBC SQL Server Driver][SQL Server]Attempt to fetch logical page (1:0) in database 'MyProject' belongs to object 'ALLOCATION', not to object 'syscomments'.
------

As I said, the SP works in my other machine and only when I move it over to this one that the error pops up.

ideas anyone?

JP|||This error occurs when SQL detcts any database corruption and to determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. Also check the error log for other errors, which often accompany a 605 error.

For more information on CHECKDB refer to books online.

My suggestion is to keep database in DBO Use only until you resolve the corruption on the database, do not allow any other process to deal with until this gets fixed.

HTH|||Originally posted by Satya
This error occurs when SQL detcts any database corruption and to determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. Also check the error log for other errors, which often accompany a 605 error.

For more information on CHECKDB refer to books online.

My suggestion is to keep database in DBO Use only until you resolve the corruption on the database, do not allow any other process to deal with until this gets fixed.

HTH

I tried correcting the db is single-user mode but when i tried to execute

dbcc checkdb ('MyProject', REPAIR_ALLOW_DATA_LOSS )

it notifies me that I should be in single-user mode which I already am and won't continue.!

perhaps I should just reinstall SQL... good thing I keep a script of table creation and sp procedures.

JP|||Make sure you haven't opened or accessed same DB in EM and QA.
Its not necessarily to have DB in singel-user mode when running DBCC CHECKDB, you can kill any other process which is involved to access during this execution.|||Originally posted by Satya
Make sure you haven't opened or accessed same DB in EM and QA.
Its not necessarily to have DB in singel-user mode when running DBCC CHECKDB, you can kill any other process which is involved to access during this execution.

I'm sure i haven't got any connections to it. I just finished installing it and still same errors... *sigh*|||I downloaded the same DB from another machine and to my surprise this was not corrupt at all. Perhaps its the target machine where I uploaded it to that caused the error. There are so many factors that I would not be surprised a simple thing such as these may be the cause in the first place.

thanks for the checkdb info.

JP|||If the problem persists from Database there is no use if SQL Server is reinstalled. Try to fix the corruption on the database level.

As you've scripts for the database, export important data using DTS to a text file and recreate the DB using scripts and import using DTS, it may work.

Meanwhile have a sneak thru SQL Error log for any information.

All the best.|||the good thing is that my main development machine is at my home office and the test box is here at work.

I'm not too concerned about the data for now because I'm still writing the program but I have tried to fix the corruption at the db level but quite honestly, the error log doesn't tell me anything more than what was displayed when I ran the cehckdb script anyway and even if I tried, i can't get it to fix it.

JP|||For the database corruption its suggested to use DBCC CHECKDB and check for event viewer also for any hardware issues or harddisk problems.|||I understand. I did mention it in my original post along with what the event viewer recorded.

anyway, when i have some time, I'll investigate further.

thanks,

JP

Error at statup

Hello all,
I'm getting an error when starting SQL2K SP3 running on
Windows 2K Server.
The error message is in a message box called "Queue
Manager" with an ! in a triangle and the following text:
Run-time error '-2147467259 (80004005)':
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Has anyone else come across this error and what did you do
to correct it?
At this point the server will not start up, I get this
message when i'm trying to manually start the SQL Server
as it will not start up with the OS as it is supposed to
do.
Background: No changes have been made too the server
configuration. Database structure's have been changed.
I've looked through all the Microsoft KB's but other
problems with this error message dont seem to relate to
this particular scenario. I'm afraid I might have to
reinstall SQL2K. This could be a problem, might not get
all the data back. However, I do have the MDF and LDF.
Any help is appreciated.
Thanks
Isaiah* What account are you using to startup?
* Is SQL SErver set for mixed mode authentication?
* Have you tried running it as an application using the '-c' switch from
command prompt?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error Applying SP3 to SQL 2000

My development server has four instances of SQL Server. They all show up as
build 760 so I assumed they were all at SP3a. However, when I went to apply
MS03-031 only three of the four instances showed up as being eligible to
apply which I did. I decided to reapply SP3a to the second instance (the one
that didn't show up in the list). When I did this I got an error indicating
a problem with the stored procedure sp_vupgrade_replication. We don't use
replication on this server so I'm not sure why the error occurred. the log
shows "[DDBNETLIB]General Network Error. Check your network documentation."
and "[DBNETLIB]ConnectionRead (recv())."
Can anyone help? Thanks.
> My development server has four instances of SQL Server. They all show up
as
> build 760 so I assumed they were all at SP3a. However, when I went to
apply
> MS03-031 only three of the four instances showed up as being eligible to
> apply which I did. I decided to reapply SP3a to the second instance (the
one
> that didn't show up in the list). When I did this I got an error
indicating
> a problem with the stored procedure sp_vupgrade_replication. We don't
use
> replication on this server so I'm not sure why the error occurred. the
log
> shows "[DDBNETLIB]General Network Error. Check your network
documentation."
> and "[DBNETLIB]ConnectionRead (recv())."
> Can anyone help? Thanks.
You should check the original setup log for SQL Server 2000 sp3
installation to find out if there were any errors encountered during the
installation.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Wednesday, February 15, 2012

Error Adding SQL Server Login Properties

Hello,
I have SQL 200 SP3 box that has a web app with a hard coded user; I
tried to re-add the user after it was deleted.
I now get the following error when trying to add the database access:
"Error 21002 [SQL-DMO] user 'unsername' already exists."
Any help would be greatly appreciated.
I fixed my issue by running the following:
use my_db;
go
sp_change_users_login AUTO_FIX, 'my_user'
go
Hulicat wrote:
> Hello,
> I have SQL 200 SP3 box that has a web app with a hard coded user; I
> tried to re-add the user after it was deleted.
> I now get the following error when trying to add the database access:
> "Error 21002 [SQL-DMO] user 'unsername' already exists."
>
> Any help would be greatly appreciated.

Error Adding SQL Server Login Properties

Hello,
I have SQL 200 SP3 box that has a web app with a hard coded user; I
tried to re-add the user after it was deleted.
I now get the following error when trying to add the database access:
"Error 21002 [SQL-DMO] user 'unsername' already exists."
Any help would be greatly appreciated.I fixed my issue by running the following:
use my_db;
go
sp_change_users_login AUTO_FIX, 'my_user'
go
Hulicat wrote:
> Hello,
> I have SQL 200 SP3 box that has a web app with a hard coded user; I
> tried to re-add the user after it was deleted.
> I now get the following error when trying to add the database access:
> "Error 21002 [SQL-DMO] user 'unsername' already exists."
>
> Any help would be greatly appreciated.