Proclarity Installation using SQL Server 2005

Hi,

I'm attempting to install Proclarity 6 on a Win2003 Virtual PC, using SQL Server 2005 as my DB platform.

The installation continually fails with the error: "The SQL Serve Selected is not in Mixed Mode...". This occurs even if i specify the 'sa' account during the installation.

My SQL Sever is definitely set to Mixed Mode authentication!

Has anyone come accross this before and is there a fix?

Thanks in advance,

Leigh.

just run this statement and see whether its returning 0 or not

select SERVERPROPERTY('IsIntegratedSecurityOnly')

Madhu

|||

Hi Madhu,

I ran that statement and got 0 back from the server suggesting that i am indeed running in "Mixed Mode".

Cheers,

Leigh

|||

Well, i'm not sure why, but i've applied SQL 2005 SP2 and created a new user which i specified to run the ProClarity installation and hey-presto, suddenly everything works!

Cheers,
Leigh

Process task hangs running bcp

We are attempting to use Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00 to run a BCP command from a Process task. We are able to do so without a problem when running it interactively, but when run as a SQL Server Agent job the bcp process never completes and the job hangs indefinitely.

We also tried using a Script task for this, with the same result.

Has anyone else run into this problem?

Thanks,

Ron

What happens if you run it from dtexec? (i.e. from the command-line).

If it executes successfully using dtexec then its most likely a security issue.

-Jamie

|||

Jamie,

Thank you for your reply. Yes, the BCP processing works fine when I run the package interactively in Management Studio. However, I don't see how it could be a security issue, because the account that SQL Server Agent is running under is in the Administrators group on the server, and the BCP output is going to a share on that same server. I double checked, and the Administrators group has full control permission on both the share and the folder.

Is there anyone that has been successful in running BCP in an SSIS Process task under SQL Server Agent?

Thanks,

Ron

|||this link might help: http://support.microsoft.com/kb/918760|||

Thank you for the suggestion, Duane. In this case, though, the package executes, it just hangs on the Process task that executes the BCP command.

The security level of the package is DontSaveSensitive, and the Agent service account has full permissions to the file system, so it does not seem likely that lack of permissions is the issue.

Ron

|||

We stumbled upon the solution for this, but it does seem that a glitch in SSIS may be the root cause.

When running BCP in a Process task, the path to the BCP executable must be provided. When running a package interactively a UNC path name to bcp.exe works fine, but when run as a job the UNC path name somehow causes the process to hang indefinitely. Changing the notation from "\\<servername>\c$\Program Files\..." to "c:\Program Files\..." fixes the problem.

Is there any valid reason that this should be the case?

Thanks,

Ron

Process ID 65 attempting to unlock unowned resource

Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
I am getting the above error in the event log for my website.
Can someone help me and tell me what this means?
thansk in Advance. Kim
Hi
See if this applies:
http://support.microsoft.com/?kbid=814654
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net. ..
> Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> I am getting the above error in the event log for my website.
> Can someone help me and tell me what this means?
> thansk in Advance. Kim
>
|||Hi,
It looks to be the exact problem - except we are running with service pak 4
here's the version info
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Developer
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
> Hi
> See if this applies:
> http://support.microsoft.com/?kbid=814654
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net. ..
>
|||Hi
You are running Windows SP4, but SQL Server SP3 (8.00.760)
The problem was fixed in build 765 which was after SP3.
You can do one of the following:
Download the Security Hotfix Rollup that will take you build to 818
(http://www.microsoft.com/downloads/d...displaylang=en)
Download build 878,
http://support.microsoft.com/default...b;en-us;838166
Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
your server is not using AWE or PAE as there is a known issue with it and
SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
http://msmvps.com/epprecht/archive/2.../14/46940.aspx
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net.. .
> Hi,
> It looks to be the exact problem - except we are running with service pak
> 4
> here's the version info
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
>
|||Hi,
Thanks for your help.
I will pass this on to the guy who will do the updates.
Kim
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eoxzWthWFHA.2976@.TK2MSFTNGP10.phx.gbl...
> Hi
> You are running Windows SP4, but SQL Server SP3 (8.00.760)
> The problem was fixed in build 765 which was after SP3.
> You can do one of the following:
> Download the Security Hotfix Rollup that will take you build to 818
>
(http://www.microsoft.com/downloads/d...ae9d-bd44-40c5
-add3-b8c99618e68d&displaylang=en)[vbcol=seagreen]
> Download build 878,
> http://support.microsoft.com/default...b;en-us;838166
> Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
> your server is not using AWE or PAE as there is a known issue with it and
> SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
> http://msmvps.com/epprecht/archive/2.../14/46940.aspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net.. .
pak
>

Process ID 65 attempting to unlock unowned resource

Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
I am getting the above error in the event log for my website.
Can someone help me and tell me what this means?
thansk in Advance. KimHi
See if this applies:
http://support.microsoft.com/?kbid=814654
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
> Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> I am getting the above error in the event log for my website.
> Can someone help me and tell me what this means?
> thansk in Advance. Kim
>|||Hi,
It looks to be the exact problem - except we are running with service pak 4
here's the version info
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Developer
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
> Hi
> See if this applies:
> http://support.microsoft.com/?kbid=814654
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
> > Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> >
> > I am getting the above error in the event log for my website.
> > Can someone help me and tell me what this means?
> >
> > thansk in Advance. Kim
> >
> >
>|||Hi
You are running Windows SP4, but SQL Server SP3 (8.00.760)
The problem was fixed in build 765 which was after SP3.
You can do one of the following:
Download the Security Hotfix Rollup that will take you build to 818
(http://www.microsoft.com/downloads/details.aspx?FamilyID=9814ae9d-bd44-40c5-add3-b8c99618e68d&displaylang=en)
Download build 878,
http://support.microsoft.com/default.aspx?scid=kb;en-us;838166
Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
your server is not using AWE or PAE as there is a known issue with it and
SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
http://msmvps.com/epprecht/archive/2005/05/14/46940.aspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
> Hi,
> It looks to be the exact problem - except we are running with service pak
> 4
> here's the version info
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
>> Hi
>> See if this applies:
>> http://support.microsoft.com/?kbid=814654
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Kim" <kim@.xxx.com> wrote in message
>> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
>> > Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
>> >
>> > I am getting the above error in the event log for my website.
>> > Can someone help me and tell me what this means?
>> >
>> > thansk in Advance. Kim
>> >
>> >
>>
>|||Hi,
Thanks for your help.
I will pass this on to the guy who will do the updates.
Kim
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eoxzWthWFHA.2976@.TK2MSFTNGP10.phx.gbl...
> Hi
> You are running Windows SP4, but SQL Server SP3 (8.00.760)
> The problem was fixed in build 765 which was after SP3.
> You can do one of the following:
> Download the Security Hotfix Rollup that will take you build to 818
>
(http://www.microsoft.com/downloads/details.aspx?FamilyID=9814ae9d-bd44-40c5
-add3-b8c99618e68d&displaylang=en)
> Download build 878,
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838166
> Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
> your server is not using AWE or PAE as there is a known issue with it and
> SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
> http://msmvps.com/epprecht/archive/2005/05/14/46940.aspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
> > Hi,
> > It looks to be the exact problem - except we are running with service
pak
> > 4
> > here's the version info
> >
> > Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> > Copyright (c) 1988-2003 Microsoft Corporation Developer
> > Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
> >> Hi
> >>
> >> See if this applies:
> >>
> >> http://support.microsoft.com/?kbid=814654
> >>
> >> Regards
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> IM: mike@.epprecht.net
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >> "Kim" <kim@.xxx.com> wrote in message
> >> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
> >> > Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> >> >
> >> > I am getting the above error in the event log for my website.
> >> > Can someone help me and tell me what this means?
> >> >
> >> > thansk in Advance. Kim
> >> >
> >> >
> >>
> >>
> >
> >
>

Process ID 65 attempting to unlock unowned resource

Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
I am getting the above error in the event log for my website.
Can someone help me and tell me what this means?
thansk in Advance. KimHi
See if this applies:
http://support.microsoft.com/?kbid=814654
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
> Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> I am getting the above error in the event log for my website.
> Can someone help me and tell me what this means?
> thansk in Advance. Kim
>|||Hi,
It looks to be the exact problem - except we are running with service pak 4
here's the version info
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Developer
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
> Hi
> See if this applies:
> http://support.microsoft.com/?kbid=814654
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
>|||Hi
You are running Windows SP4, but SQL Server SP3 (8.00.760)
The problem was fixed in build 765 which was after SP3.
You can do one of the following:
Download the Security Hotfix Rollup that will take you build to 818
(http://www.microsoft.com/downloads/...&displaylang=en)
Download build 878,
http://support.microsoft.com/defaul...kb;en-us;838166
Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
your server is not using AWE or PAE as there is a known issue with it and
SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
http://msmvps.com/epprecht/archive/...5/14/46940.aspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
> Hi,
> It looks to be the exact problem - except we are running with service pak
> 4
> here's the version info
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
>|||Hi,
Thanks for your help.
I will pass this on to the guy who will do the updates.
Kim
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eoxzWthWFHA.2976@.TK2MSFTNGP10.phx.gbl...
> Hi
> You are running Windows SP4, but SQL Server SP3 (8.00.760)
> The problem was fixed in build 765 which was after SP3.
> You can do one of the following:
> Download the Security Hotfix Rollup that will take you build to 818
>
(http://www.microsoft.com/downloads/...4ae9d-bd44-40c5
-add3-b8c99618e68d&displaylang=en)
> Download build 878,
> http://support.microsoft.com/defaul...kb;en-us;838166
> Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
> your server is not using AWE or PAE as there is a known issue with it and
> SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
> http://msmvps.com/epprecht/archive/...5/14/46940.aspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
pak[vbcol=seagreen]
>