Error installing Reporting Services

Hi,
Trying to install the developer's version of Reporting Services on Windows
2003 Server with SQL Server 2000 SP3.
I click on SETUP.EXE and the very first dialog box comes up and says:
Software components to install:
>Microsoft SQL Server Reporting Services Setup Support Files
Error!
Cancel is the only option.
Any ideas?
Thx.
Andy JacobsTry copying the install Dir to the local machine and running from there.
"Andy Jacobs" <Andy Jacobs@.discussions.microsoft.com> wrote in message
news:0F5ABAE6-C353-4C14-951C-1E577F73B814@.microsoft.com...
> Hi,
> Trying to install the developer's version of Reporting Services on Windows
> 2003 Server with SQL Server 2000 SP3.
> I click on SETUP.EXE and the very first dialog box comes up and says:
> Software components to install:
> >Microsoft SQL Server Reporting Services Setup Support Files
> Error!
> Cancel is the only option.
> Any ideas?
> Thx.
> Andy Jacobs
>
>|||I don't know why, but this is very slooooooooooow. As you say, the install
form displays only a cancel button. Wait... Go get a cup of coffee... Tell
the joke of the day to the guy in the next cube... The continue button will
be displayed in a Microsoft second. I think this bad design by Bill's boys.
The cancel button should not be enabled until the install software figures
out what it's going to allow. A lot of folks probably hit Cancel
prematurely.
"Andy Jacobs" <Andy Jacobs@.discussions.microsoft.com> wrote in message
news:0F5ABAE6-C353-4C14-951C-1E577F73B814@.microsoft.com...
> Hi,
> Trying to install the developer's version of Reporting Services on Windows
> 2003 Server with SQL Server 2000 SP3.
> I click on SETUP.EXE and the very first dialog box comes up and says:
> Software components to install:
> >Microsoft SQL Server Reporting Services Setup Support Files
> Error!
> Cancel is the only option.
> Any ideas?
> Thx.
> Andy Jacobs
>
>

Error Installing JDBC SP3 on Windows 2003

Hello all,
I'm running into an error when I try to install JDBC SP3 on my Windows 2003
server. I'm currently running JDBC SP2, but when the installer begins to
install the files, I'm prompted with a message box asking for the location to
"Microsoft SQL Server 2000 Driver for JDBC SP2.msi". I don't have this file,
nor can I find it on my system. All I have is the Setup.exe file that you
download off of the Microsoft site. Has anyone seen this error before and
know how to get around it? Also, it should be noted that if I try to remove
JDBC SP2 from Add / Remove Programs, I'm prompted with the same message box.
Thanks,
Jason
Hmm... weird error. The .msi file is compressed within the JDBC driver
setup.exe package. It usually resides in C:\Documents and
Settings\userX\Local Settings\Temp\_isSomethingOrOther
However, the files and folder are deleted once installation is complete or
aborted.You could try running setup.exe then finding and copying the folder
to another location and use that later.
hth.
joe.
"Jason Delaune" <JasonDelaune@.discussions.microsoft.com> wrote in message
news:96990E9D-3617-4D2A-82F9-E6AF689B7578@.microsoft.com...
> Hello all,
> I'm running into an error when I try to install JDBC SP3 on my Windows
> 2003
> server. I'm currently running JDBC SP2, but when the installer begins to
> install the files, I'm prompted with a message box asking for the location
> to
> "Microsoft SQL Server 2000 Driver for JDBC SP2.msi". I don't have this
> file,
> nor can I find it on my system. All I have is the Setup.exe file that you
> download off of the Microsoft site. Has anyone seen this error before and
> know how to get around it? Also, it should be noted that if I try to
> remove
> JDBC SP2 from Add / Remove Programs, I'm prompted with the same message
> box.
> Thanks,
> Jason
|||Joe,
That did the trick. I installed the SP2 driver on my PC and before I clicked
Finish at the end of the install, I copied the temporary folder off to the
server. I then ran the SP3 setup and pointed to the SP2 MSI when prompted,
and the installer continued on. Thanks for your help!!
Jason
"Joe Yong" wrote:

> Hmm... weird error. The .msi file is compressed within the JDBC driver
> setup.exe package. It usually resides in C:\Documents and
> Settings\userX\Local Settings\Temp\_isSomethingOrOther
> However, the files and folder are deleted once installation is complete or
> aborted.You could try running setup.exe then finding and copying the folder
> to another location and use that later.
> hth.
>
> joe.
>
> "Jason Delaune" <JasonDelaune@.discussions.microsoft.com> wrote in message
> news:96990E9D-3617-4D2A-82F9-E6AF689B7578@.microsoft.com...
>
>
sql

Error in loading big file

Hi All,
I have an application on WL8.1 with sp3, the database is SQL Server 2000. I
have code below to load local file into database. The data type in database
is image.
PreparedStatement pStatement = null;
InputStreammyStream myStream = new InputStream();
myStream.setEmbeddedStream( is );
pStatement.setBinaryStream( 1, myStream, -1 );
pStatement.executeUpdate();
pStatement.close();
pStatement = null;
is is InputStream from a local file and the sql statement is
insert into file_content(content) values(?)
This workes fine for the files with size less than 150M, but for those big
files (>150M), it doesn't work and I got error message as below:
<Feb 11, 2005 12:00:41 PM PST> <Notice> <EJB> <BEA-010014> <Error occurred
while attempting to rollback transaction:
javax.transaction.SystemException: Heuristic hazard:
(weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
(javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
been closed.))
javax.transaction.SystemException: Heuristic hazard:
(weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
(javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
been closed.))
at weblogic.transaction.internal.ServerTransactionImp l.internalRollback
(ServerTransactionImpl.java:396)
at weblogic.transaction.internal.ServerTransactionImp l.rollback
(ServerTransactionImpl.java:362)
Any body can help? Thanks in advance.
Message posted via http://www.sqlmonster.com
Fred Wang via SQLMonster.com wrote:

> Hi All,
> I have an application on WL8.1 with sp3, the database is SQL Server 2000. I
> have code below to load local file into database. The data type in database
> is image.
> PreparedStatement pStatement = null;
> InputStreammyStream myStream = new InputStream();
> myStream.setEmbeddedStream( is );
> pStatement.setBinaryStream( 1, myStream, -1 );
> pStatement.executeUpdate();
> pStatement.close();
> pStatement = null;
> is is InputStream from a local file and the sql statement is
> insert into file_content(content) values(?)
> This workes fine for the files with size less than 150M, but for those big
> files (>150M), it doesn't work and I got error message as below:
> <Feb 11, 2005 12:00:41 PM PST> <Notice> <EJB> <BEA-010014> <Error occurred
> while attempting to rollback transaction:
> javax.transaction.SystemException: Heuristic hazard:
> (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
> (javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
> been closed.))
> javax.transaction.SystemException: Heuristic hazard:
> (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
> (javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
> been closed.))
> at weblogic.transaction.internal.ServerTransactionImp l.internalRollback
> (ServerTransactionImpl.java:396)
> at weblogic.transaction.internal.ServerTransactionImp l.rollback
> (ServerTransactionImpl.java:362)
> Any body can help? Thanks in advance.
>
Hi. That means the DBMS choked on the submission and killed the whole
JDBC connection. Check your DBMS log for problems. You may be running
out of space in the DBMS's transaction log, which must have a separate
copy of your insert data, to prepare for DBMS commit or rollback.
Joe Weinstein at BEA
|||Thanks Joe. I do agree. So what shall I do? We don't have idea how big
could the file be. Is there any way we may cut file into smaller pieces,
ship the to db and reassembly there? Thanks a lot
Message posted via http://www.sqlmonster.com
|||Fred Wang via SQLMonster.com wrote:
> Thanks Joe. I do agree. So what shall I do? We don't have idea how big
> could the file be. Is there any way we may cut file into smaller pieces,
> ship the to db and reassembly there? Thanks a lot
Well, there might be some ugly hacks, but fundamentally you just want to
get some SQLServer DBA help to configure it so it will handle the type of
transaction you want to do. An RDBMS isn't usually ideal as a store for
huge blobs... Sort of like using the bank to deposit those huge polynesian
coral wheel money tokens. Even the islanders stopped moving them around.
One sunk in a bay while being transported by boat, so they just left it there,
and people just started agreeing on who owned it at any time... ;)
Joe Weinstein at BEA
|||| From: "Fred Wang via SQLMonster.com" <forum@.SQLMonster.com>
| Subject: Error in loading big file
| Date: Fri, 11 Feb 2005 23:13:31 GMT
| Organization: http://www.SQLMonster.com
| Message-ID: <2f0972878fc74c0f8e40521ba0ad6ae3@.SQLMonster.com >
| X-Abuse-Report: http://www.SQLMonster.com/Uwe/NB/Abuse.aspx
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: 178.67-18-207.reverse.theplanet.com 67.18.207.178
| Lines: 1
| Path:
TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFT NGP08.phx.gbl!tk2msftngp13
.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:866
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| Hi All,
| I have an application on WL8.1 with sp3, the database is SQL Server 2000.
I
| have code below to load local file into database. The data type in
database
| is image.
|
| PreparedStatement pStatement = null;
| InputStreammyStream myStream = new InputStream();
| myStream.setEmbeddedStream( is );
| pStatement.setBinaryStream( 1, myStream, -1 );
| pStatement.executeUpdate();
| pStatement.close();
| pStatement = null;
|
| is is InputStream from a local file and the sql statement is
| insert into file_content(content) values(?)
|
| This workes fine for the files with size less than 150M, but for those big
| files (>150M), it doesn't work and I got error message as below:
|
| <Feb 11, 2005 12:00:41 PM PST> <Notice> <EJB> <BEA-010014> <Error occurred
| while attempting to rollback transaction:
| javax.transaction.SystemException: Heuristic hazard:
| (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
| (javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
| been closed.))
| javax.transaction.SystemException: Heuristic hazard:
| (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard,
| (javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver]Object has
| been closed.))
| at weblogic.transaction.internal.ServerTransactionImp l.internalRollback
| (ServerTransactionImpl.java:396)
| at weblogic.transaction.internal.ServerTransactionImp l.rollback
| (ServerTransactionImpl.java:362)
|
| Any body can help? Thanks in advance.
|
| --
| Message posted via http://www.sqlmonster.com
|
You could insert the new data in chunks by calling UPDATETEXT multiple
times. From Java, you could iteratively call read() on a FileInputStream
object and populate a byte array buffer. For each iteration, you can
execute the stored procedure below and pass the buffer as an input
parameter. This operation may not be logged, depending on the recovery
model of your database (simple or bulk-logged). This may be the way to go
to avoid excessive transaction log usage. However, the downfall is that
you do not get the benefit of a transaction, so a failure along the way
would leave the BLOB data in an incomplete state.
T-SQL
======
CREATE TABLE FredWang([ID] INT PRIMARY KEY, [blob] IMAGE)
GO
INSERT INTO FredWang VALUES(1, CONVERT(VARBINARY(8000), ''))
GO
CREATE PROCEDURE usp_InsertBlob
(
@.row BIGINT,
@.insertOffset INT = NULL,
@.deleteLength INT = 0,
@.data VARBINARY(8000)
)
AS
BEGIN
DECLARE @.textPointer BINARY(16)
SELECT @.textPointer = TEXTPTR(blob) FROM FredWang WHERE [ID] = @.row
DECLARE @.query VARCHAR(4000)
UPDATETEXT FredWang.blob @.textPointer @.insertOffset @.deleteLength @.data
END
GO
Java
=====
import java.sql.*;
import java.io.*;
public class query
{
public static void main(String[] args) throws Exception
{
Connection conn = null;
PreparedStatement pstmt = null;
ResultSet rs = null;
int chunkSize = 8000;
try
{
// Load the JDBC driver
Class.forName("com.microsoft.jdbc.sqlserver.SQLSer verDriver");
// Connect to SQL Server
String url =
"jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=jdbc;";
conn = DriverManager.getConnection(url, "sa", "password");
// Load the file into memory
FileInputStream file = new FileInputStream("c:\\large_file.jpg");
// Insert the BLOB data in chunks
String sql = "EXEC usp_InsertBlob 1, DEFAULT, DEFAULT, ?";
pstmt = conn.prepareStatement(sql, ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
byte [] buff = new byte[chunkSize];
while(file.read(buff) != -1)
{
pstmt.setBytes(1, buff);
pstmt.executeUpdate();
}
file.close();
}
catch (SQLException sqlEx)
{
while (sqlEx != null)
{
System.out.println("SQLState: " + sqlEx.getSQLState());
System.out.println("Message: " + sqlEx.getMessage());
System.out.println("Error code: " + sqlEx.getErrorCode());
sqlEx = sqlEx.getNextException();
System.out.println();
}
}
catch(Exception e)
{
e.printStackTrace();
}
finally
{
// Cleanup
if (rs != null)
rs.close();
rs = null;
if (pstmt != null)
pstmt.close();
pstmt = null;
if (conn != null)
conn.close();
conn = null;
}
}
}
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 ?E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
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 in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..
17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
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 in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
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 in EM

When I click on property of Db in EM on a sql server EM
quit.
I have installed the sp3 recently.
Anyone has the same problem?
How to fix?
Thank you
Have you tried installing the security patch MS03-031? It
includes a fix for an issue similar to what you are
describing. You can find more details in the following
article:
http://support.microsoft.com/?id=814113
-Sue
On Mon, 11 Oct 2004 09:24:46 -0700, "Gianluca Danielli"
<gianluca.danielli@.tin.it> wrote:

>When I click on property of Db in EM on a sql server EM
>quit.
>I have installed the sp3 recently.
>Anyone has the same problem?
>How to fix?
>Thank you

Error in Application log

Windows XP Pro and SQL Server Personal 2000 with sp3
I get three errors that are very similar
I would appreciate some guidance
Unprotection of auditable protected data.
Data Description: SQL Server Registration
Key Identifier: 96b4b79c-9197-4c12-a733-d773753fedd8
Protected Data Flags: 0x0
Protection Algorithms: 3DES-168 , SHA1-160
Failure Reason: 0x8009000B
For more information, see Help and Support Center atHi Mark,
The problem seems to be related to Protected Storage and password, OS
security feature. Have you performed an administrative password reset or
change password?
On Windows XP, Protected Storage uses the user's password exclusively to
encrypt user data, such as RSA private keys for current user key container.
Whenever the user password is changed, Protected Storage subsystem is
automatically notified of
this event, and is supplied with both the old and new passwords. This
allows Protected Storage to decrypt all of its master keys with the old
password, and re-encrypt them using the new password.
Prior to Windows XP, a machine secret was used by Protected Storage to
encrypt the master RSA keys rather than the user password exclusively.
Using a machine secret made Protected Storage more robust, but the user
data could be accessed by anyone with local administrative access to the
machine.
If you use the standard change password mechanism by entering the old and
new passwords, everything will work fine. If you performed an
administrative password reset, the old password is not available, and so
access to the master keys is lost. This is by design in Windows XP. In this
scenario, CryptAcquireContext() API will fail with NTE_BAD_KEYSET
(80090016), even if the key container already exists and the caller has
permissions to open the key container.
You will also get a "Failure Audit" 599 Event ID in the Security Log with
the following description
Unprotection of auditable protected data.
Data Description: Export Flag
Key Identifier: 38fb8fc8-7c1e-40bc-aa8f-00d94ef0056e
Protected Data Flags: 0x0
Protection Algorithms: 3DES-168 , SHA1-160
Failure Reason: 0x8009000B
It is best to post in Windows-specific newsgroups for accurate information.
I am providing the information based on my research.
1. One could use Password Recovery Disk as explained in Q290260, if the
customer already made one and if this is a Windows XP-based computer that
is member of a workgroup.
2. If the user puts their password back to what it was originally when the
key container/RSA key pair was initially created, then everything will work
fine thereafter.
290260 EFS, Credentials, and Private Keys from Certificates Are Unavailable
http://support.microsoft.com/?id=290260
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| From: "Mark A Gregory" <mgregory@.gt.com.au>
| Subject: Error in Application log
| Date: Fri, 1 Aug 2003 22:13:48 +1000
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <u8JveZCWDHA.1480@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 203.34.248.5
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:299038
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Windows XP Pro and SQL Server Personal 2000 with sp3
|
| I get three errors that are very similar
| I would appreciate some guidance
|
|
| Unprotection of auditable protected data.
|
| Data Description: SQL Server Registration
|
| Key Identifier: 96b4b79c-9197-4c12-a733-d773753fedd8
|
| Protected Data Flags: 0x0
|
| Protection Algorithms: 3DES-168 , SHA1-160
|
| Failure Reason: 0x8009000B
|
|
|
| For more information, see Help and Support Center at
|
|
||||Hi Mark,
The problem seems to be related to Protected Storage and password, OS
security feature. Have you performed an administrative password reset or
change password?
It is best to re-post this issue in Windows-specific newsgroups for
accurate information since this newsgroup focuses on SQL Server specific
issues only.
I've included some information for your reference based on my research.
1. One could use Password Recovery Disk as explained in Q290260, if the
customer already made one and if this is a Windows XP-based computer that
is member of a workgroup.
2. If the user puts their password back to what it was originally when the
key container/RSA key pair was initially created, then everything will work
fine thereafter.
290260 EFS, Credentials, and Private Keys from Certificates Are Unavailable
http://support.microsoft.com/?id=290260
If the information does not help, please re-post in the
microsoft.public.windowsxp.security_admin or
microsoft.public.windowsxp.general for a better response. The reason why we
recommend posting appropriately is you will get the most qualified pool of
respondents, and other customers who use the newsgroups regularly can
either share their knowledge or learn from your interaction with us.
On Windows XP, Protected Storage uses the user's password exclusively to
encrypt user data, such as RSA private keys for current user key container.
Whenever the user password is changed, Protected Storage subsystem is
automatically notified of this event, and is supplied with both the old and
new passwords. This allows Protected Storage to decrypt all of its master
keys with the old password, and re-encrypt them using the new password.
Prior to Windows XP, a machine secret was used by Protected Storage to
encrypt the master RSA keys rather than the user password exclusively.
Using a machine secret made Protected Storage more robust, but the user
data could be accessed by anyone with local administrative access to the
machine.
If you use the standard change password mechanism by entering the old and
new passwords, everything will work fine. If you performed an
administrative password reset, the old password is not available, and so
access to the master keys is lost. This is by design in Windows XP. In this
scenario, CryptAcquireContext() API will fail with NTE_BAD_KEYSET
(80090016), even if the key container already exists and the caller has
permissions to open the key container.
You will also get a "Failure Audit" 599 Event ID in the Security Log with
the following description
Unprotection of auditable protected data.
Data Description: Export Flag
Key Identifier: 38fb8fc8-7c1e-40bc-aa8f-00d94ef0056e
Protected Data Flags: 0x0
Protection Algorithms: 3DES-168 , SHA1-160
Failure Reason: 0x8009000B
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| From: "Mark A Gregory" <mgregory@.gt.com.au>
| Subject: Error in Application log
| Date: Fri, 1 Aug 2003 22:13:48 +1000
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <u8JveZCWDHA.1480@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 203.34.248.5
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:299038
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Windows XP Pro and SQL Server Personal 2000 with sp3
|
| I get three errors that are very similar
| I would appreciate some guidance
|
|
| Unprotection of auditable protected data.
|
| Data Description: SQL Server Registration
|
| Key Identifier: 96b4b79c-9197-4c12-a733-d773753fedd8
|
| Protected Data Flags: 0x0
|
| Protection Algorithms: 3DES-168 , SHA1-160
|
| Failure Reason: 0x8009000B
|
|
|
| For more information, see Help and Support Center at
|
|
|

Error ID 19011

Platform: Windows 2000 Server SP3
Hi,
I noticed the following error event in the Application Log
of our database server (SQL 2000 Server SP3) for the first
time three days ago:
Error ID: 19011
Source: MSSQLServer
SuperSocket info: ConnectionListen(Shared-Memory (LPC)) :
Error 5.
This error appeared right after I shut down and restarted
the database, using the SQL Server Service Manager. I
always do this to backup the database, but never get the
error message.
I would appreciate if anyone could help.
ThanksAmir\
This is comment of Bill Cheng [MSFT]
According to my check, "SpnRegister" is to register in Active Directory.
8344 indicates insufficient access rights to perform the operation.
According to my experience, if the account starting SQL Server service does
not have enough permissions, it may also this message: SuperSocket Info:
Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013 (An
attempt was made to access a socket in a way forbidden by its access
permissions.).
Could you check the account that starts SQL Server service? Make sure it
has enough permissions. Try to add it to LOCAL ADMINISTRATORS group to
check.
For more information on DsWriteAccountSpn ,visit the following Microsoft
website:
http://msdn.microsoft.com/library/d...-us/netdir/ad/d
swriteaccountspn.asp
"Amir M." <anonymous@.discussions.microsoft.com> wrote in message
news:df0901c40b68$d7e17d80$a501280a@.phx.gbl...
> Platform: Windows 2000 Server SP3
> Hi,
> I noticed the following error event in the Application Log
> of our database server (SQL 2000 Server SP3) for the first
> time three days ago:
> Error ID: 19011
> Source: MSSQLServer
> SuperSocket info: ConnectionListen(Shared-Memory (LPC)) :
> Error 5.
> This error appeared right after I shut down and restarted
> the database, using the SQL Server Service Manager. I
> always do this to backup the database, but never get the
> error message.
> I would appreciate if anyone could help.
> Thanks
>|||Thanks for the reply.
If it's a permission issue, then why the error message
didn't used to appear before?
Do you know how to find out the name of the SQL account?
Is it an account that was created by someone or is it
built in? Is it a domain account?
Thanks

>--Original Message--
>Amir\
>This is comment of Bill Cheng [MSFT]
>According to my check, "SpnRegister" is to register in
Active Directory.
>8344 indicates insufficient access rights to perform the
operation.
>According to my experience, if the account starting SQL
Server service does
>not have enough permissions, it may also this message:
SuperSocket Info:
>Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) :
Error 10013 (An
>attempt was made to access a socket in a way forbidden by
its access
>permissions.).
>Could you check the account that starts SQL Server
service? Make sure it
>has enough permissions. Try to add it to LOCAL
ADMINISTRATORS group to
>check.
>For more information on DsWriteAccountSpn ,visit the
following Microsoft
>website:
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/netdir/ad/d
>swriteaccountspn.asp
>
>
>
>"Amir M." <anonymous@.discussions.microsoft.com> wrote in
message
>news:df0901c40b68$d7e17d80$a501280a@.phx.gbl...
Log
first
(LPC)) :
restarted
>
>.
>

error help:Remote access not allowed for Windows NT user activated by SETUSER

Hi,

I just install SP3 for our SQL Server 2000 yesterday.After that, I have problem using xp_sendmail.
I have a stored procedure in Server A that getting result from Server B.
In Query Analyzer, I can successfully execute procedure A.(exec procedure_name)
However, if I put it in xp_sendmail command...(exec sp_sendmail email_address ,@.query='exec procedure_name'),
I got an error message saying 'ODBC error 7410 (42000) Remote access not allowed for Windows NT user activated by SETUSER.'

But before I upgrade, that xp_sendmail works fine for more than one month.

BTW,if in xp_sendmail, I only get result from local server, it works perfect fine.

How can I make it work?

Thanks in advance.you can put the result of the SP into a global temp table (or permanant one) and select from that in the xp_sendmail.

Don't have 2 sp3 systems here to see what's wrong it but praobably will tomorrow.
Does the profiler show anything interesting?