Showing posts with label msg. Show all posts
Showing posts with label msg. Show all posts

Sunday, March 11, 2012

"SQL Server Registation failed

hi! at first, am having problem with sql server registration.
Am getting the following msg when trying to do sql server
registration :
"SQL Server Registation failed ....
SQL Server does not exist or access denied
ConnectionOpen(Connect())"
After reading through the related discussions posted to this
workgroup. I'm able to create an alias and added in the sql
server registration to the sql server successfully.
Now the problem is that for that SQL server, it's becoming
very slow when i try to browse through the items in the
enterprise manager until it's stop responding.
It's even faster to access that sql
server through another server(with sql installed also) which
i added in the server registration and access it remotely.
Any idea what's wrong with that server? Thks!
"SQL Server Registation failed ....
SQL Server does not exist or access denied
ConnectionOpen(Connect())"
If I understand your question correctly, you are saying that when you open
SQL Enterprise Manager on one Client1 and connect to Server1, it browses
extremely slowly. However if you open Enterprise Manager on Client2 and
connect to Server1, everything is fine. If this is true, then this could be
an issue with your client1 machine (and not the server).
You should check -
1. What other apps are running on Client1. Is there some type of memory
pressure causing this behavior?
2. Is there a possible network problem between Client1 and Server1? If this
is the case then most likely you will see erratic behavior at other times
and with other apps connecting to SQL also.
If you still suspect that it is your server that is slow, you could run
Profiler trace on Server1 to see what happens when you open the SQL
Enterprise Manager on Client1 (as opposed to Client2)
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||hi!
what i meant is that i opened the sql enterprise manager from the sql server
itself is slow. When i access it remotely by opening antoher sql enterprise
manager from another sql serverit's fine.
what;s Profiler trace? where to run this program thk~
"Pankaj Agarwal [MSFT]" wrote:

> If I understand your question correctly, you are saying that when you open
> SQL Enterprise Manager on one Client1 and connect to Server1, it browses
> extremely slowly. However if you open Enterprise Manager on Client2 and
> connect to Server1, everything is fine. If this is true, then this could be
> an issue with your client1 machine (and not the server).
> You should check -
> 1. What other apps are running on Client1. Is there some type of memory
> pressure causing this behavior?
> 2. Is there a possible network problem between Client1 and Server1? If this
> is the case then most likely you will see erratic behavior at other times
> and with other apps connecting to SQL also.
> If you still suspect that it is your server that is slow, you could run
> Profiler trace on Server1 to see what happens when you open the SQL
> Enterprise Manager on Client1 (as opposed to Client2)
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>

"SQL Server Registation failed

hi! at first, am having problem with sql server registration.
Am getting the following msg when trying to do sql server
registration :
"SQL Server Registation failed ....
SQL Server does not exist or access denied
ConnectionOpen(Connect())"
After reading through the related discussions posted to this
workgroup. I'm able to create an alias and added in the sql
server registration to the sql server successfully.
Now the problem is that for that SQL server, it's becoming
very slow when i try to browse through the items in the
enterprise manager until it's stop responding.
It's even faster to access that sql
server through another server(with sql installed also) which
i added in the server registration and access it remotely.
Any idea what's wrong with that server? Thks!
"SQL Server Registation failed ....
SQL Server does not exist or access denied
ConnectionOpen(Connect())"If I understand your question correctly, you are saying that when you open
SQL Enterprise Manager on one Client1 and connect to Server1, it browses
extremely slowly. However if you open Enterprise Manager on Client2 and
connect to Server1, everything is fine. If this is true, then this could be
an issue with your client1 machine (and not the server).
You should check -
1. What other apps are running on Client1. Is there some type of memory
pressure causing this behavior?
2. Is there a possible network problem between Client1 and Server1? If this
is the case then most likely you will see erratic behavior at other times
and with other apps connecting to SQL also.
If you still suspect that it is your server that is slow, you could run
Profiler trace on Server1 to see what happens when you open the SQL
Enterprise Manager on Client1 (as opposed to Client2)
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||hi!
what i meant is that i opened the sql enterprise manager from the sql server
itself is slow. When i access it remotely by opening antoher sql enterprise
manager from another sql serverit's fine.
what;s Profiler trace? where to run this program thk~
"Pankaj Agarwal [MSFT]" wrote:
> If I understand your question correctly, you are saying that when you open
> SQL Enterprise Manager on one Client1 and connect to Server1, it browses
> extremely slowly. However if you open Enterprise Manager on Client2 and
> connect to Server1, everything is fine. If this is true, then this could be
> an issue with your client1 machine (and not the server).
> You should check -
> 1. What other apps are running on Client1. Is there some type of memory
> pressure causing this behavior?
> 2. Is there a possible network problem between Client1 and Server1? If this
> is the case then most likely you will see erratic behavior at other times
> and with other apps connecting to SQL also.
> If you still suspect that it is your server that is slow, you could run
> Profiler trace on Server1 to see what happens when you open the SQL
> Enterprise Manager on Client1 (as opposed to Client2)
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>

Thursday, March 8, 2012

"query notification" problem

I am using query notification and have the following problem:
I tegister once, then change the DB table manually to test. a msg is printed
to the log proving the call back function was called. I can repeat this
several time.
BUT, I then go away for 10 min', and come back. Now, when I change the data
in the DB nothing happens!
any clue how to fix and undertand this?
thanksUPDATE:
I used trace to see what is going on in the database. So I see that I get
"subscription fired" followed by "subscription registered" everytime I do
changes to the database.
After I stop doing any changes to the database for 5 minuts, and re-change
the data there, I see the database fire the "subscription fired" event, but
this time there is no "subscription registered" event. I also do not get the
log printout that I have in my web ASP.NET application, that is supposed to
write a line in the callback function.
So the hear is the deal:
The callback function gets the event fired for the first few times, so I am
doing the registration right. but, somehting happens to the ASP.NET
aplication, or the DB connection or something, that causes the callback
function not to be called after a certain time. anyone has an idea of what
am I up against? why is this happening?
thanks|||Any idea what is this error I get?
The query notification dialog on conversation handle
'{2FD61BF6-44B8-DA11-8B4E-00123F74CFF6}.' closed due to the following error:
'<?xml version="1.0"?><Error
xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Co
de><Description>Cannot
find the remote service
'SqlQueryNotificationService-657d36e5-7654-44a2-8137-5ec5e3417cc4'
because it does not exist.</Description></Error>'.
?|||It means that service named
'SqlQueryNotificationService-657d36e5-7654-44a2-8137-5ec5e3417cc4' does not
exist in the database where the notifications should be delivered to. Seems
like you are adding the broker instance at the end of the service name. The
service name you pass to the SqlNotificationRequest.Options must match the
service name you created in the database.
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"csmba" <csmba@.nowhere.com> wrote in message
news:u4e2l3fTGHA.3192@.TK2MSFTNGP09.phx.gbl...
> Any idea what is this error I get?
> The query notification dialog on conversation handle
> '{2FD61BF6-44B8-DA11-8B4E-00123F74CFF6}.' closed due to the following
> error: '<?xml version="1.0"?><Error
> xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</
Code><Description>Cannot
> find the remote service
> 'SqlQueryNotificationService-657d36e5-7654-44a2-8137-5ec5e3417cc4&apo
s;
> because it does not exist.</Description></Error>'.
>
> ?
>

Tuesday, March 6, 2012

"Order by" error running DBCC DBREINDEX

I'm running a simple DBCC DBREINDEX ('myTable') and I receive the
following error:

"Server: Msg 169, Level 15, State 2, Line 2
A column has been specified more than once in the order by list.
Columns in the order by list must be unique. DBCC execution
completed. If DBCC printed error messages, contact your system
administrator."

I can successfully reindex other tables in this database. I thought
that perhaps I had objects in the database that ended up with the same
name, but I've pretty much ruled that out.

Any suggestions?

Thanks
John D. Morris
mailto://jmorris_42@.hotmail.comjmorris_42@.hotmail.com (John Morris) wrote in message news:<5b4367be.0308050426.10612a9f@.posting.google.com>...
> I'm running a simple DBCC DBREINDEX ('myTable') and I receive the
> following error:
> "Server: Msg 169, Level 15, State 2, Line 2
> A column has been specified more than once in the order by list.
> Columns in the order by list must be unique. DBCC execution
> completed. If DBCC printed error messages, contact your system
> administrator."
> I can successfully reindex other tables in this database. I thought
> that perhaps I had objects in the database that ended up with the same
> name, but I've pretty much ruled that out.
> Any suggestions?
> Thanks
> John D. Morris
> mailto://jmorris_42@.hotmail.com

Followup:

As it turns out, I had a hidden "Hypothetical" index that the index
tuning wizard decided not to clean up when it was done. The only way
to see the index was in sp_helpindex. It did not appear in the object
browser. MS claims this was fixed in SP1...I guess not. Anyway,
dropped the hypothetical index and all is well.

-jdm|||John,

Can you consistently repro the bug?
--
Arun Marathe
Microsoft Corporation

Disclaimers:
(1) This posting is provided "AS IS" with no warranties, and confers no
rights.
(2) Use of included script samples are subject to the terms specified at:
http://www.microsoft.com/info/cpyright.htm

"John D. Morris" <jmorris@.sni.org> wrote in message
news:d034511a.0308051015.60cc849a@.posting.google.c om...
> jmorris_42@.hotmail.com (John Morris) wrote in message
news:<5b4367be.0308050426.10612a9f@.posting.google.com>...
> > I'm running a simple DBCC DBREINDEX ('myTable') and I receive the
> > following error:
> > "Server: Msg 169, Level 15, State 2, Line 2
> > A column has been specified more than once in the order by list.
> > Columns in the order by list must be unique. DBCC execution
> > completed. If DBCC printed error messages, contact your system
> > administrator."
> > I can successfully reindex other tables in this database. I thought
> > that perhaps I had objects in the database that ended up with the same
> > name, but I've pretty much ruled that out.
> > Any suggestions?
> > Thanks
> > John D. Morris
> > mailto://jmorris_42@.hotmail.com
> Followup:
> As it turns out, I had a hidden "Hypothetical" index that the index
> tuning wizard decided not to clean up when it was done. The only way
> to see the index was in sp_helpindex. It did not appear in the object
> browser. MS claims this was fixed in SP1...I guess not. Anyway,
> dropped the hypothetical index and all is well.
> -jdm

"Order by" clause

I run the script below in sql2005 and am receiving the error msg 209. Do I
need a prefix to order by either STATE, TAXAMNT, or SUBTOTAL because I want
them displyed in front.
Thank you.
Charlie
select STATE, TAXAMNT, SUBTOTAL, *
from sop30200
where state in('NJ','NY','WA','CO','CA','ME','OK','VA','PA','T N')
AND SOPTYPE IN (3,4)
AND DOCDATE between '2007-02-01 00:00:00.000' and '2007-02-28 00:00:00.000'
--AND TAXEXMT1 = ' '
AND SUBTOTAL <> 0
--AND SOPNUMBE LIKE 'NCINV%'
AND VOIDSTTS = 0
AND SOPNUMBE NOT IN
(SELECT INVNO
FROM VERTEX..REGPRERETURNSTBL
WHERE COMPCD = 'ABS'
and invno between '20070201' and '20070228')
--AND SHIPTOGEOCODE LIKE '31%')
ORDER BY STATE DESC
Msg 209, Level 16, State 1, Line 1
Ambiguous column name 'STATE'.
While there is no actual ambiguity, the parser is not so sure.
Your select list contains the STATE column twice: once
explicitly as the first column and once again in the *. The
parser does not know whether you want to sort on the
source column sop30200.STATE or on the output column
STATE. They are the same in this query, but there are
queries where they could be different because some
output expression or column is aliased as STATE. The
parser does not try to figure out the meaning of the query.
There are two solutions. One is to specify
ORDER BY sop30200.STATE
and the other is to list all the columns you want in the output
separately and one each, not using the * notation. The second
solution is the better one, at least in production, because neither
* nor duplicate columns in the output are typically a good idea.
But if this is just a quick ad hoc query, the first solution is fine.
-- Steve Kass
-- Drew University
-- http://www.stevekass.com
chas2006 wrote:

>I run the script below in sql2005 and am receiving the error msg 209. Do I
>need a prefix to order by either STATE, TAXAMNT, or SUBTOTAL because I want
>them displyed in front.
>Thank you.
>Charlie
>select STATE, TAXAMNT, SUBTOTAL, *
>from sop30200
>where state in('NJ','NY','WA','CO','CA','ME','OK','VA','PA','T N')
>AND SOPTYPE IN (3,4)
>AND DOCDATE between '2007-02-01 00:00:00.000' and '2007-02-28 00:00:00.000'
>--AND TAXEXMT1 = ' '
>AND SUBTOTAL <> 0
>--AND SOPNUMBE LIKE 'NCINV%'
>AND VOIDSTTS = 0
>AND SOPNUMBE NOT IN
>(SELECT INVNO
>FROM VERTEX..REGPRERETURNSTBL
>WHERE COMPCD = 'ABS'
>and invno between '20070201' and '20070228')
>--AND SHIPTOGEOCODE LIKE '31%')
>ORDER BY STATE DESC
>
>Msg 209, Level 16, State 1, Line 1
>Ambiguous column name 'STATE'.
>

Saturday, February 25, 2012

"must declare variable" when variable has been declared!

Any idea why the following message is returned?

Server: Msg 137, Level 15, State 2, Line 5
Must declare the variable '@.table'.

The script is created to run through each column in the database and check it against cross referenced data in other table. It had to be built because of the database we own has not a single referntial constraint in it (long story but it's from the the age old "our code works better than a well designed database" school of thought).

excuse the poorly laid out SQL - it's hard to copy and paste into this thing...

Thanks
Yal

------------------------

SET NOCOUNT ON

DECLARE @.table VARCHAR(32)
,@.column VARCHAR(32)
,@.x_table VARCHAR(32)
,@.x_column VARCHAR(32)
,@.x_type VARCHAR(32)
,@.problem VARCHAR(32)
,@.count VARCHAR(32)

DECLARE xref_check CURSOR FOR
SELECT table_name, column_name, xref_table, xref_column, xref_type
FROM xref_check

OPEN xref_check
FETCH NEXT FROM xref_check INTO @.table, @.column, @.x_table, @.x_column, @.x_type

WHILE @.@.FETCH_STATUS = 0
BEGIN

IF @.x_table = 'PS_XREF'
BEGIN
-- SELECT @.table, @.column, @.x_table, @.x_column, @.x_type
EXEC ('IF (SELECT COUNT('+ @.column +')
FROM '+ @.table +'
WHERE '+ @.column + ' NOT IN (SELECT code FROM PS_XREF WHERE type = '''+ @.x_type +''')) > 0
BEGIN
SELECT @.table, @.column, @.x_table, @.x_column, @.x_type, x.'+ @.column +'
FROM '+ @.table +' x
WHERE '+ @.column + ' NOT IN (SELECT code FROM PS_XREF WHERE type = '''+ @.x_type +''')
END'
)

END

ELSE
BEGIN
-- SELECT @.table, @.column, @.x_table, @.x_column, @.x_type
EXEC ('IF (SELECT COUNT('+ @.column +')
FROM '+ @.table +'
WHERE '+ @.column + ' NOT IN (SELECT '+ @.x_column +' FROM '+ @.x_table +')) > 0
BEGIN
SELECT @.table, @.column, @.x_table, @.x_column, @.x_type, x.'+ @.column +'
FROM '+ @.table +' x
WHERE '+ @.column + ' NOT IN (SELECT '+ @.x_column +' FROM '+ @.x_table +')
END')
END

FETCH NEXT FROM xref_check INTO @.table, @.column, @.x_table, @.x_column, @.x_type

END

CLOSE xref_check
DEALLOCATE xref_checkMake sure your references to these variables exist outside the string. For example:

@.x_type +''')) > 0
BEGIN
SELECT @.table, @.column, @.x_table, @.x_column, @.x_type, x.'

should have @.table, @.column ... outside the string like you did before this statement.

Sunday, February 19, 2012

"Internal SQL Server error."

"Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line 58
Internal SQL Server error."
...and on that note, I'm going home.
What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
What is on line 58?
"Mike C#" <xyz@.xyz.com> wrote in message
news:uOisHvzEHHA.3608@.TK2MSFTNGP02.phx.gbl...
> "Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line
> 58
> Internal SQL Server error."
> ...and on that note, I'm going home.
>
|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:e66wS1zEHHA.3784@.TK2MSFTNGP02.phx.gbl...
> What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
> What is on line 58?
Hi Aaron,
Don't sweat it. This is a stored procedure that ran fine about 20 times in
a row on SQL 2000 SP 4. The 21st time seems to have been the charm. I
already checked and there's no KB articles that address this particular
situation (though there are a few that talk about "Internal Server Error"
under different circumstances that don't apply to my situation.)
BTW, Line 58 looks like this: DECLARE @.s VARCHAR(50)
Cool, huh? Thanks.
|||> already checked and there's no KB articles that address this particular
> situation (though there are a few that talk about "Internal Server Error"
> under different circumstances that don't apply to my situation.)
Most "Internal Server Error" issues are internal bugs that are fixed with
SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
that addressed a different system (not all bugs ever make it to the
knowledge base, so don't consider it to be gospel).
But, if you want to stay at SP4 and ignore the more recent hotfixes, you may
still continue to have this problem. If you can reproduce it on a second
box, especially after applying the latest hotfix, you may want to post a bug
on connect.
A
|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23SYpze8EHHA.4016@.TK2MSFTNGP02.phx.gbl...
> Most "Internal Server Error" issues are internal bugs that are fixed with
> SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
> that addressed a different system (not all bugs ever make it to the
> knowledge base, so don't consider it to be gospel).
> But, if you want to stay at SP4 and ignore the more recent hotfixes, you
> may still continue to have this problem. If you can reproduce it on a
> second box, especially after applying the latest hotfix, you may want to
> post a bug on connect.
Thanks, I was just venting For now I've rebooted the box and it
suddenly works again. Go figure. I'll probably post a bug if it happens
again.
Thanks again
|||> Thanks, I was just venting
You should consider a blog.
Here, just about everything is presumed to be a request for help.
A

"Internal SQL Server error."

"Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line 58
Internal SQL Server error."
...and on that note, I'm going home.What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
What is on line 58?
"Mike C#" <xyz@.xyz.com> wrote in message
news:uOisHvzEHHA.3608@.TK2MSFTNGP02.phx.gbl...
> "Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line
> 58
> Internal SQL Server error."
> ...and on that note, I'm going home.
>|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:e66wS1zEHHA.3784@.TK2MSFTNGP02.phx.gbl...
> What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
> What is on line 58?
Hi Aaron,
Don't sweat it. This is a stored procedure that ran fine about 20 times in
a row on SQL 2000 SP 4. The 21st time seems to have been the charm. I
already checked and there's no KB articles that address this particular
situation (though there are a few that talk about "Internal Server Error"
under different circumstances that don't apply to my situation.)
BTW, Line 58 looks like this: DECLARE @.s VARCHAR(50)
Cool, huh? Thanks.|||> already checked and there's no KB articles that address this particular
> situation (though there are a few that talk about "Internal Server Error"
> under different circumstances that don't apply to my situation.)
Most "Internal Server Error" issues are internal bugs that are fixed with
SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
that addressed a different system (not all bugs ever make it to the
knowledge base, so don't consider it to be gospel).
But, if you want to stay at SP4 and ignore the more recent hotfixes, you may
still continue to have this problem. If you can reproduce it on a second
box, especially after applying the latest hotfix, you may want to post a bug
on connect.
A|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:%23SYpze8EHHA.4016@.TK2MSFTNGP02.phx.gbl...
> Most "Internal Server Error" issues are internal bugs that are fixed with
> SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
> that addressed a different system (not all bugs ever make it to the
> knowledge base, so don't consider it to be gospel).
> But, if you want to stay at SP4 and ignore the more recent hotfixes, you
> may still continue to have this problem. If you can reproduce it on a
> second box, especially after applying the latest hotfix, you may want to
> post a bug on connect.
Thanks, I was just venting For now I've rebooted the box and it
suddenly works again. Go figure. I'll probably post a bug if it happens
again.
Thanks again|||> Thanks, I was just venting
You should consider a blog.
Here, just about everything is presumed to be a request for help.
A

"Internal SQL Server error."

"Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line 58
Internal SQL Server error."
...and on that note, I'm going home.What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
What is on line 58?
"Mike C#" <xyz@.xyz.com> wrote in message
news:uOisHvzEHHA.3608@.TK2MSFTNGP02.phx.gbl...
> "Server: Msg 8624, Level 16, State 7, Procedure p_get_LocalAuthor2, Line
> 58
> Internal SQL Server error."
> ...and on that note, I'm going home.
>|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:e66wS1zEHHA.3784@.TK2MSFTNGP02.phx.gbl...
> What does SELECT @.@.VERSION yield? What does p_get_LocalAuthor2 look like?
> What is on line 58?
Hi Aaron,
Don't sweat it. This is a stored procedure that ran fine about 20 times in
a row on SQL 2000 SP 4. The 21st time seems to have been the charm. I
already checked and there's no KB articles that address this particular
situation (though there are a few that talk about "Internal Server Error"
under different circumstances that don't apply to my situation.)
BTW, Line 58 looks like this: DECLARE @.s VARCHAR(50)
Cool, huh? Thanks.|||> already checked and there's no KB articles that address this particular
> situation (though there are a few that talk about "Internal Server Error"
> under different circumstances that don't apply to my situation.)
Most "Internal Server Error" issues are internal bugs that are fixed with
SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
that addressed a different system (not all bugs ever make it to the
knowledge base, so don't consider it to be gospel).
But, if you want to stay at SP4 and ignore the more recent hotfixes, you may
still continue to have this problem. If you can reproduce it on a second
box, especially after applying the latest hotfix, you may want to post a bug
on connect.
A|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23SYpze8EHHA.4016@.TK2MSFTNGP02.phx.gbl...
>> already checked and there's no KB articles that address this particular
>> situation (though there are a few that talk about "Internal Server Error"
>> under different circumstances that don't apply to my situation.)
> Most "Internal Server Error" issues are internal bugs that are fixed with
> SPs or hotfixes. It may very well be a symptom that is fixed by a hotfix
> that addressed a different system (not all bugs ever make it to the
> knowledge base, so don't consider it to be gospel).
> But, if you want to stay at SP4 and ignore the more recent hotfixes, you
> may still continue to have this problem. If you can reproduce it on a
> second box, especially after applying the latest hotfix, you may want to
> post a bug on connect.
Thanks, I was just venting :) For now I've rebooted the box and it
suddenly works again. Go figure. I'll probably post a bug if it happens
again.
Thanks again|||> Thanks, I was just venting :)
You should consider a blog.
Here, just about everything is presumed to be a request for help.
A

Thursday, February 16, 2012

"Failed to obtain TransactionDispenserInterface"

This msg. appears in the startup messages in Errorlog.
Failed to obtain TransactionDispenserInterface: Result
Code = 0x8004d01b
It occurs about the 10th line in Errorlog and follows:
Attempting to initialize Distributed Transaction
Coordinator.
What causes it? How to fix it?
(SQL Server 7.0, SP4, NT 4.0)
Thank you.This error is reported if the MSDTC service is not running
when SQL starts. Makse sure the MSDTC service is
running and set it's startup to automatic if it's required
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bd" <bruce.drechsler@.delphi.com> wrote in message
news:098c01c34bd0$69906f60$a001280a@.phx.gbl...
This msg. appears in the startup messages in Errorlog.
Failed to obtain TransactionDispenserInterface: Result
Code = 0x8004d01b
It occurs about the 10th line in Errorlog and follows:
Attempting to initialize Distributed Transaction
Coordinator.
What causes it? How to fix it?
(SQL Server 7.0, SP4, NT 4.0)
Thank you.|||MSDTC is not required at this time. I'll consider the
messages informational, only.
Thank you.
Bruce
>--Original Message--
>This error is reported if the MSDTC service is not running
>when SQL starts. Makse sure the MSDTC service is
>running and set it's startup to automatic if it's required
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"bd" <bruce.drechsler@.delphi.com> wrote in message
>news:098c01c34bd0$69906f60$a001280a@.phx.gbl...
>This msg. appears in the startup messages in Errorlog.
>Failed to obtain TransactionDispenserInterface: Result
>Code = 0x8004d01b
>It occurs about the 10th line in Errorlog and follows:
>Attempting to initialize Distributed Transaction
>Coordinator.
>What causes it? How to fix it?
>(SQL Server 7.0, SP4, NT 4.0)
>Thank you.
>
>.
>

Monday, February 13, 2012

"Error!" msg during "setup support files" installation

Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
"Error!" msg during "setup support files" installation.
Unable to install Reporting Services. Found a couple of users experiencing
the same problem, but no solution :( Any ideas?
/ChrisFirst, check the error log in Event Viewer and see if you can find any
EventID number for your error. That can pinpoint what the error really is.
If it's error 25619, then check if the DTC service is running? Go check in
services.msc for "Distributed Transaction Coordinator".
Even if it says "started", it might not be. I've had some troubles with
installing RS, and the DTC was the culprit.
It's been discussed in this thread:
http://groups.google.com/groups?hl=en&lr=&threadm=89FD4D17-1F6A-4BCF-A15E-CF098C5A68D7%40microsoft.com&rnum=1
In this thread, Pitroda asks about a password for Network Service. Just
leave the password blank, at least that worked for me.
Kaisa M. Lindahl
"Chris Leaf" <ChrisLeaf@.discussions.microsoft.com> wrote in message
news:E6F567CB-08C9-4B49-8544-9DB32826CC09@.microsoft.com...
> Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
> "Error!" msg during "setup support files" installation.
> Unable to install Reporting Services. Found a couple of users experiencing
> the same problem, but no solution :( Any ideas?
> /Chris|||Event log says:
"Product: Microsoft SQL Server 2000 Reporting Services Enterprise Edition --
Please install SQL Server by running setup.exe."
and
"Product: Microsoft SQL Server 2000 Reporting Services Enterprise Edition --
Installation failed."
install log ends with:
<Func Name='SqlSetupFilesComp::Install'>
<Func Name='BootstrapPackageLogic'>
<Func Name='InstallBootstrapPackage'>
/I "D:\Setup\bootmsi.dat" REBOOT="ReallySuppress"
ADDLOCAL="BootstrapFiles,WatsonFiles,ParsFiles1033,HelpFiles1028,HelpFiles1031,HelpFiles1033,HelpFiles1036,HelpFiles1040,HelpFiles1041,HelpFiles1042,HelpFiles2052,HelpFiles3082,WatsonFiles1033" /qn
<EndFunc Name='InstallBootstrapPackage' Return='1603' GetLastError='183'>
<EndFunc Name='BootstrapPackageLogic' Return='1603' GetLastError='183'>
SqlSetupFilesComp BootstrapPackageLogic() failed : (1603)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:565}
SCU_SetupMgr::svc() caught exception: SqlSetupFilesComp
BootstrapPackageLogic() failed : (1603)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:565}. SetupMgr:
state=ERROR, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0,
custom_props={AutoStart=true
HandleReboots=false
ModuleDir=D:
QuietMode=false
Unattended=false
WorkDir=D:
}} {n:\rosetta\dev\src\everettsetup\sqlcu\dll\scusetupmgr.cpp:428}
ScuProgressDlg::SetupFinished()
ScuProgressDlg::DialogProc() installation done... waiting for setup mgr
<EndFunc Name='UpdateComponents' Return='1602' GetLastError='0'>
DTC is running..
Thanks for your response.
"Kaisa M. Lindahl" wrote:
> First, check the error log in Event Viewer and see if you can find any
> EventID number for your error. That can pinpoint what the error really is.
> If it's error 25619, then check if the DTC service is running? Go check in
> services.msc for "Distributed Transaction Coordinator".
> Even if it says "started", it might not be. I've had some troubles with
> installing RS, and the DTC was the culprit.
> It's been discussed in this thread:
> http://groups.google.com/groups?hl=en&lr=&threadm=89FD4D17-1F6A-4BCF-A15E-CF098C5A68D7%40microsoft.com&rnum=1
> In this thread, Pitroda asks about a password for Network Service. Just
> leave the password blank, at least that worked for me.
> Kaisa M. Lindahl
> "Chris Leaf" <ChrisLeaf@.discussions.microsoft.com> wrote in message
> news:E6F567CB-08C9-4B49-8544-9DB32826CC09@.microsoft.com...
> > Windows 2003 Server. Asp.Net 1.1. Sql Server 2000 Sp3a.
> >
> > "Error!" msg during "setup support files" installation.
> > Unable to install Reporting Services. Found a couple of users experiencing
> > the same problem, but no solution :( Any ideas?
> >
> > /Chris
>
>

Thursday, February 9, 2012

"Best" error messages contest

Server: Msg 1015, Level 15, State 1, Line 1
An aggregate cannot appear in an ON clause unless it is in a subquery
contained in a HAVING clause or select list, and the column being aggregated
is an outer reference.Why not to post the statement also?
AMB
"Ian Boyd" wrote:

> Server: Msg 1015, Level 15, State 1, Line 1
> An aggregate cannot appear in an ON clause unless it is in a subquery
> contained in a HAVING clause or select list, and the column being aggregat
ed
> is an outer reference.
>
>|||Cause it was querying a view, with a self aggregate join. It wouldn't make
sense.
Besides, that's not the contest.

> Why not to post the statement also?|||"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:%23iiDq5LTFHA.3840@.tk2msftngp13.phx.gbl...
> Server: Msg 1015, Level 15, State 1, Line 1
> An aggregate cannot appear in an ON clause unless it is in a subquery
> contained in a HAVING clause or select list, and the column being
> aggregated is an outer reference.
>
RAISERROR('Two guys walk into a bar...',0,1)|||Q: "Who Killed the Monkey in Raiders of the Lost Ark?"
A: "Bad Date."
"Chris Hohmann" <nospam@.thankyou.com> wrote in message
news:eUuKDXOTFHA.584@.TK2MSFTNGP15.phx.gbl...
> "Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
> news:%23iiDq5LTFHA.3840@.tk2msftngp13.phx.gbl...
> RAISERROR('Two guys walk into a bar...',0,1)
>|||"Michael C#" <howsa@.boutdat.com> wrote in message
news:uQjzyhOTFHA.2520@.TK2MSFTNGP09.phx.gbl...
> Q: "Who Killed the Monkey in Raiders of the Lost Ark?"
> A: "Bad Date."
> "Chris Hohmann" <nospam@.thankyou.com> wrote in message
> news:eUuKDXOTFHA.584@.TK2MSFTNGP15.phx.gbl...
>
Dilbert: What color do you want that database?
PHB: I think mauve has more RAM.

"Bad variable type" error msg can't get past it.

I posted this here a few days ago, and someone said to ask on a delphi
forum. Well, I did, and also have searched everywhere I can imagine,
without luck.
My stored proc when executed from delphi 7 produces a Bad variable type
error. This happens on win2k and win98, but does not happen on XP.
It runs from query analyser both on XP and on win2k. It runs in the app on
XP.
The app creates the parameters for the sp component and assigns data types,
which I've verified match the sp.
Clearly no one here knows the exact answer, or you would have said it by
now. So how about more ideas about where to look?
JeremyHi
I assume you are using ADO? Have you checked out MDAC consistency and
versions? Have you SET NOCOUNT ON?
You may also want to post some code and DDL.
John
"JeremyGrand" wrote:

> I posted this here a few days ago, and someone said to ask on a delphi
> forum. Well, I did, and also have searched everywhere I can imagine,
> without luck.
> My stored proc when executed from delphi 7 produces a Bad variable type
> error. This happens on win2k and win98, but does not happen on XP.
> It runs from query analyser both on XP and on win2k. It runs in the app o
n
> XP.
> The app creates the parameters for the sp component and assigns data types
,
> which I've verified match the sp.
> Clearly no one here knows the exact answer, or you would have said it by
> now. So how about more ideas about where to look?
> Jeremy
>
>|||Yes, ADO. MDAC is the latest, and the win2k sps are up to date.
I will try setting nocount on. How might this help?
Here's the table I'm inserting into:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[AGNT_STATMENT]') and OBJECTPROPERTY(id, N'IsUserTable') =
1)
drop table [dbo].[AGNT_STATMENT]
GO
CREATE TABLE [dbo].[AGNT_STATMENT] (
[StatementNumber] [bigint] NOT NULL ,
[Item] [smallint] NOT NULL ,
[DatePosted] [smalldatetime] NULL ,
[Type] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Debit] [float] NULL ,
[Credit] [float] NULL ,
[Balance] [float] NULL ,
[Description] [varchar] (25) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[LoanNo] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Prefix] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Certificate] [varchar] (12) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CommissionPercent] [float] NULL ,
[FeeDr] [money] NULL ,
[FeeCr] [money] NULL ,
[EntryDate] [smalldatetime] NULL ,
[Department] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PaymentStatementNumber] [bigint] NULL ,
[PaymentItem] [int] NULL ,
[PaymentAmount] [money] NULL ,
[PaymentFee] [money] NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[AGNT_STATMENT] WITH NOCHECK ADD
CONSTRAINT [PK_AGNT_STATMENT] PRIMARY KEY CLUSTERED
(
[StatementNumber],
[Item]
) ON [PRIMARY]
GO
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:18DADDD6-1A68-4615-97AB-55A502A51176@.microsoft.com...
> Hi
> I assume you are using ADO? Have you checked out MDAC consistency and
> versions? Have you SET NOCOUNT ON?
> You may also want to post some code and DDL.
> John
> "JeremyGrand" wrote:
>|||Hi
I would not expect SET NOCOUNT ON to make a difference unless you are
looking at returning a result set. It is not clear if you have are looking a
t
the same database/server when you experience the problem. It is also not
clear if it happens every time on the platforms that it does not work on. If
this is the same server then it points to a local problem on the clients tha
t
fail.
You may want to run SQL Profiler to see what is being sent to the database.
At a guess the most likely cause would be the date/time or money values whic
h
could be effected by the regional settings.
John
"John Bell" wrote:
> Hi
> I assume you are using ADO? Have you checked out MDAC consistency and
> versions? Have you SET NOCOUNT ON?
> You may also want to post some code and DDL.
> John
> "JeremyGrand" wrote:
>|||John, Profiler output is interesting. The trace seems to only show the
steps up to but not including the execution of the problem stored proc. I
have the execution wrapped in a try-block, and an exception is thrown. I
don't see evidence of this in the profiler trace. I've searched the output
and can't find any reference to the stored proc in question.
So, this probably implies that my ado component is not happy with the data
or parameters I'm feeding it.
On the other hand, I can consistently reproduce the error on the only 2
win2k machines I've tested, and it also is reported to fail on a win98
machine. The program consistently runs without error on at least 2 XP
machines, so this seems very OS dependent.
I've looked at regional settings (money, dates) on my own w2k machine, and
they seem normal.
I did a trace while running the stored proc on an XP machine. Here's the
line where the sp executes. Nothing leaps out at me, but maybe someone will
see something.
exec agnt_statment_InsertNew 261, NULL, 'CAN', 0.000000000000000e+000,
5.050000000000000e+002, -2.072300000000000e+004, 'XQN000000055',
'72AG99-143', 'XQN', '000000055', 3.500000000000000e+001,
0.000000000000000e+000, 0.000000000000000e+000, 'Nov 1 2005
12:00:00:000AM', '', NULL, NULL, 0.000000000000000e+000,
0.000000000000000e+000
-Jeremy

> You may want to run SQL Profiler to see what is being sent to the
> database.
> At a guess the most likely cause would be the date/time or money values
> which
> could be effected by the regional settings.
> John
>|||Hi
Are you tracing the start events?
You may want to try creating a dummy procedure with the same parameters and
see if that works, you may have to return a default result set. It will rule
out the parameter passing. You could try hard coding the parameters that you
listed and seeing if it works, then change the values to be dynamic one at a
time, alternatively you could try remove each parameter one at a time until
you don't get the error.
John
"JeremyGrand" wrote:

> John, Profiler output is interesting. The trace seems to only show the
> steps up to but not including the execution of the problem stored proc. I
> have the execution wrapped in a try-block, and an exception is thrown. I
> don't see evidence of this in the profiler trace. I've searched the output
> and can't find any reference to the stored proc in question.
> So, this probably implies that my ado component is not happy with the data
> or parameters I'm feeding it.
> On the other hand, I can consistently reproduce the error on the only 2
> win2k machines I've tested, and it also is reported to fail on a win98
> machine. The program consistently runs without error on at least 2 XP
> machines, so this seems very OS dependent.
> I've looked at regional settings (money, dates) on my own w2k machine, and
> they seem normal.
> I did a trace while running the stored proc on an XP machine. Here's the
> line where the sp executes. Nothing leaps out at me, but maybe someone wi
ll
> see something.
> exec agnt_statment_InsertNew 261, NULL, 'CAN', 0.000000000000000e+000,
> 5.050000000000000e+002, -2.072300000000000e+004, 'XQN000000055',
> '72AG99-143', 'XQN', '000000055', 3.500000000000000e+001,
> 0.000000000000000e+000, 0.000000000000000e+000, 'Nov 1 2005
> 12:00:00:000AM', '', NULL, NULL, 0.000000000000000e+000,
> 0.000000000000000e+000
> -Jeremy
>
>|||John, brilliant idea. I've created a dummy program and a dummy stored proc
and am experimenting. I can actually make a program where the stored proc
succeeds by dropping a sp component on a form, whereas creating it in code
fails on w2k boxes. I guess you've gotta say that's progress!
The evidence also seems to be supporting the notion that the problem is in
delphi. There was an issue with D7.1 last year, and I'm pursuing this at
the moment.
Thanks.
Jeremy
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3FD30FD2-D288-46AD-94AB-1AF6B9ECEBCB@.microsoft.com...
> Hi
> Are you tracing the start events?
> You may want to try creating a dummy procedure with the same parameters
> and
> see if that works, you may have to return a default result set. It will
> rule
> out the parameter passing. You could try hard coding the parameters that
> you
> listed and seeing if it works, then change the values to be dynamic one at
> a
> time, alternatively you could try remove each parameter one at a time
> until
> you don't get the error.
>
> John|||Hi
"Bad variable type" is definitely generated by Delphi!
I googled this!
http://tinyurl.com/9h39b
This seems to imply you need to be very careful when choosing the datatypes
so you may not want to leave the application to do this automatically.
http://tinyurl.com/aguh8
John
"JeremyGrand" wrote:

> John, brilliant idea. I've created a dummy program and a dummy stored pro
c
> and am experimenting. I can actually make a program where the stored proc
> succeeds by dropping a sp component on a form, whereas creating it in code
> fails on w2k boxes. I guess you've gotta say that's progress!
> The evidence also seems to be supporting the notion that the problem is in
> delphi. There was an issue with D7.1 last year, and I'm pursuing this at
> the moment.
> Thanks.
> Jeremy
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3FD30FD2-D288-46AD-94AB-1AF6B9ECEBCB@.microsoft.com...
>
>|||John, good catch, these are hits I didn't find. I eventually followed the
trail to Borland's Quality Central, where it claims to be resolved, but
maybe not in Delphi 7, which is what I'm using.
However, fwiw, the solution for me seems to be to ask Delphi to enumerate
the sp's parameters (tadodataset.parameters.refresh, if you care to know),
and then I assign values in code. The app now works on w2k. Previously I
was creating the parameter objects and setting properties, and no variation
could be made to work.
Thanks for your help!
Jeremy
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:43541BEF-DFEE-4A07-9C98-90EFE2259D89@.microsoft.com...
> Hi
> "Bad variable type" is definitely generated by Delphi!
> I googled this!
> http://tinyurl.com/9h39b
> This seems to imply you need to be very careful when choosing the
> datatypes
> so you may not want to leave the application to do this automatically.
> http://tinyurl.com/aguh8
> John
>
>
> "JeremyGrand" wrote:
>