Any way around this error

I get the error (in red) below when I run this stored procedure (I'm not running in my app but in Query Analyzer) -- Please help me fix this

CREATE PROCEDURE dbo.sp_Employee_GetEmployeeLNameFNameEmpID
(
@.facilityID nvarchar(2),
@.companyID nvarchar(2),
@.deptID nvarchar(20),
@.Period int
)
AS
SELECT e.LastName + ',' + e.FirstName + ' - ' + e.EmployeeID AS ListBoxText, e.EmployeeID, e.LastName + ',' + e.FirstName AS FullName FROM Employee e
WHERE e.DeptID = @.deptID AND e.FacilityID = @.facilityID AND e.CompanyID = @.companyID AND e.EmployeeID <> (SELECT ev.EmployeeID FROM EmployeeEval ev
WHERE PeriodID= @.Period)
GO

Server: Msg 512, Level 16, State 1, Procedure sp_Employee_GetEmployeeLNameFNameEmpID, Line 9
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

WHICH employee do you want from the ev table?
It looks to me like you want a NOT IN instead:
SELECT
e.LastName + ','+ e.FirstName + ' - ' + e.EmployeeID AS ListBoxText,
e.EmployeeID,
e.LastName + ',' + e.FirstName AS FullName
FROM Employee e
WHEREe.DeptID = @.deptID
AND e.FacilityID = @.facilityID
AND e.CompanyID =@.companyID
AND e.EmployeeID NOT IN
(SELECT ev.EmployeeID
FROMEmployeeEval ev
WHERE PeriodID= @.Period)
|||

Sweet worked perfectly -- my book showed the IN part but I didn't know about the NOT IN.
Thanks a million.

Any improvements to this: Cannot apply value null to property Login: Value cannot be null.

Looks like there was a fix and then I read this fix is not a fix. Does anyone know how this can be rectified? Does it mean that only Windows authentiation is the only way it works. The Software is over 2 years old, there are no excuses.

Jayaram Krishnaswamy wrote:

Looks like there was a fix and then I read this fix is not a fix. Does anyone know how this can be rectified? Does it mean that only Windows authentiation is the only way it works. The Software is over 2 years old, there are no excuses.

Perhaps if you explained what on earth you're talking about someone could help. Explaining how you got this error would be a good place to start.

The software is 16 months old by the way.

-Jamie

Any fix for internal server error on SQLXML 3.0 and server 2003?

After developing a SQLXML SOAP app using XP pro, I've gone to deploy
it and discovered that SQLXML's SOAP doesn't seem to work on Windows
server 2003. Research on Google shows tons of people having the same
problem over the past year or so, but no solutions that seem to work.
Here's where I'm at:
- Installed Windows server 2003 + IIS 6
- Installed Soap Toolkit 3.0
- Installed SQLXML 3.0 SP2
The virtual directory is created, along with the soap virtual names
and methods. Gettings the WSDL works fine using
http://server/soap/name?WSDL , and if I allow sql= queries, the DB
connection clearly is working because
http://server/soap?sql=select+@.@.version works fine.
However, any attempt to use the actual SOAP resource results in the
infamous (and misspelled) "Internal server error occured. Request
aborted.".
The soap DLL is definitely registered; the ISAPI extension shows up in
the IIS web services extensions as allowed, and the isapi DLL is set
as the wildcard extension for the virtual directory. I've tried
putting quotes around the executable name in the configuration of the
virtual dir.
Has anyone gotten this to work, or is there definitive word that it
cannot work?
Thanks
-Brooks
I have had this exact same problem with Windows 2003. However, I have not found a solution yet. Like you, I have tried everything that has been posted in newsgroup articles but still no luck.
The use of SQLXML with Windows 2003 Server seems to be a bit middled since the instalation instructions state that the SOAP Toolkit is a pre-requisite, yet there is a Microsoft KB article (KB811215) stating that the SOAP Toolkit is only supported on Windo
ws 2003 Server for client-side components and client-side applications.
I think that Micosoft need to refresh their SQLXML information in light of Windows 2003 and the imminent withdrawl of the SOAP Toolkit.
Mark.
|||We're working on this as we speak. SqlXml included in Sql Server 2005 will
not have this requirement. We're also working on plans to release it
sooner. As soon as I have details this group will be the frist to know, I
promise!
Thanks,
Irwin
Irwin Dolobowsky
Program Manager - SqlXml
http://blogs.msdn.com/irwando
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Abrams" <anonymous@.discussions.microsoft.com> wrote in message
news:6019E7CE-3AB3-4B24-AB9B-EB7AF4D85871@.microsoft.com...
>I have had this exact same problem with Windows 2003. However, I have not
>found a solution yet. Like you, I have tried everything that has been
>posted in newsgroup articles but still no luck.
> The use of SQLXML with Windows 2003 Server seems to be a bit middled since
> the instalation instructions state that the SOAP Toolkit is a
> pre-requisite, yet there is a Microsoft KB article (KB811215) stating that
> the SOAP Toolkit is only supported on Windows 2003 Server for client-side
> components and client-side applications.
> I think that Micosoft need to refresh their SQLXML information in light of
> Windows 2003 and the imminent withdrawl of the SOAP Toolkit.
> Mark.
>