Error 911

When I try to connect to a particular database using my client/server
application I receive ERROR 911 - Server rejected the connection;
Access to the selected database has been denied.
I tried changing the owner using sp_changedbowner to a value of a
database that I can connect to but this didn't work.
I did ensure that the SQL account used to connect has permission to
the database in Enterprise Manager
I did create this database using DTS. However I can connect to the
database that was the source db w/o a problem.
ThanksHi,
Can you change the default database for this login to the database you are
trying to access. I feel that when ever you login it is going
to the Master database.
How to change this
sp_defaultdb 'UR Login name accessed by application','the database you are
trying to connect'
If it still gives error, then assign 'DB_OWNER' dataase role and try
connecting.
THanks
Hari
MCDBA
"Jim" <jromano@.phs-us.com> wrote in message
news:e1e1a687.0403261629.e32d311@.posting.google.com...
> When I try to connect to a particular database using my client/server
> application I receive ERROR 911 - Server rejected the connection;
> Access to the selected database has been denied.
> I tried changing the owner using sp_changedbowner to a value of a
> database that I can connect to but this didn't work.
> I did ensure that the SQL account used to connect has permission to
> the database in Enterprise Manager
> I did create this database using DTS. However I can connect to the
> database that was the source db w/o a problem.
> Thanks

Error 823

I am attempting to add a windows login to be able to access a database. Whe
n
I try to do this I receive the following error.
Error 823: I/O Error (bad page id) detected during read at offset
0x00000000ae6000 in file e:\program files\microsoft sql
server\mssql\master.mdf
I also receive the following when I run dbcc checkdb on the master database
Server: Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
errors for details.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) object
ID 40 index ID 2 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 40, index ID 2 due to invalid
allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
in the page header = (1:3126).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
in the page header = (0:0).
DBCC results for 'master'.
CHECKDB found 1 allocation errors and 1 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 1278 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 103 rows in 4 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 4958 rows in 94 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 2232 rows in 1213 pages for object 'syscomments'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'syscomments' (object ID 6).
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 789 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 16 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5445 rows in 31 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 14 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 46 rows in 1 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3883 rows in 166 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 38 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 3 rows in 1 pages for object 'sysservers'.
CHECKDB found 1 allocation errors and 1 consistency errors in table
'sysservers' (object ID 40).
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 28 rows in 6 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID 3407872)' (object ID 3407872).
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 730 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1111693545)' (object ID 1111693545).
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 4 allocation errors and 6 consistency errors in database
'master'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (master ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
How can I correct these errors?Before fixing it, you should check your hardware and look
for issues with your disk subsystem. Check the event logs on
the server and look for any other system errors that may
have occurred around the same time.
After fixing any hardware issues, then you would need to
restore the last known good backup of the master database.
-Sue
On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:

>I am attempting to add a windows login to be able to access a database. Wh
en
>I try to do this I receive the following error.
>Error 823: I/O Error (bad page id) detected during read at offset
>0x00000000ae6000 in file e:\program files\microsoft sql
>server\mssql\master.mdf
>I also receive the following when I run dbcc checkdb on the master database
>Server: Msg 8928, Level 16, State 6, Line 1
>Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
>errors for details.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
>page header = (0:0).
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
>errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
>errors for details.
>Server: Msg 2575, Level 16, State 1, Line 1
>IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) objec
t
>ID 40 index ID 2 but was not detected in the scan.
>Server: Msg 7965, Level 16, State 1, Line 1
>Table error: Could not check object ID 40, index ID 2 due to invalid
>allocation (IAM) page(s).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
>in the page header = (1:3126).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
>in the page header = (0:0).
>DBCC results for 'master'.
>CHECKDB found 1 allocation errors and 1 consistency errors not associated
>with any single object.
>DBCC results for 'sysobjects'.
>There are 1278 rows in 23 pages for object 'sysobjects'.
>DBCC results for 'sysindexes'.
>There are 103 rows in 4 pages for object 'sysindexes'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'sysindexes' (object ID 2).
>DBCC results for 'syscolumns'.
>There are 4958 rows in 94 pages for object 'syscolumns'.
>DBCC results for 'systypes'.
>There are 26 rows in 1 pages for object 'systypes'.
>DBCC results for 'syscomments'.
>There are 2232 rows in 1213 pages for object 'syscomments'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'syscomments' (object ID 6).
>DBCC results for 'sysfiles1'.
>There are 2 rows in 1 pages for object 'sysfiles1'.
>DBCC results for 'syspermissions'.
>There are 789 rows in 4 pages for object 'syspermissions'.
>DBCC results for 'sysusers'.
>There are 16 rows in 1 pages for object 'sysusers'.
>DBCC results for 'sysproperties'.
>There are 0 rows in 0 pages for object 'sysproperties'.
>DBCC results for 'sysdepends'.
>There are 5445 rows in 31 pages for object 'sysdepends'.
>DBCC results for 'sysreferences'.
>There are 0 rows in 0 pages for object 'sysreferences'.
>DBCC results for 'sysfulltextcatalogs'.
>There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
>DBCC results for 'sysfulltextnotify'.
>There are 0 rows in 0 pages for object 'sysfulltextnotify'.
>DBCC results for 'sysdatabases'.
>There are 14 rows in 1 pages for object 'sysdatabases'.
>DBCC results for 'sysxlogins'.
>There are 46 rows in 1 pages for object 'sysxlogins'.
>DBCC results for 'sysdevices'.
>There are 6 rows in 1 pages for object 'sysdevices'.
>DBCC results for 'sysmessages'.
>There are 3883 rows in 166 pages for object 'sysmessages'.
>DBCC results for 'sysconfigures'.
>There are 38 rows in 1 pages for object 'sysconfigures'.
>DBCC results for 'sysservers'.
>There are 3 rows in 1 pages for object 'sysservers'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table
>'sysservers' (object ID 40).
>DBCC results for 'syslanguages'.
>There are 33 rows in 3 pages for object 'syslanguages'.
>DBCC results for 'syscharsets'.
>There are 114 rows in 33 pages for object 'syscharsets'.
>DBCC results for 'sysaltfiles'.
>There are 28 rows in 6 pages for object 'sysaltfiles'.
>DBCC results for 'sysfilegroups'.
>There are 1 rows in 1 pages for object 'sysfilegroups'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table '(Objec
t
>ID 3407872)' (object ID 3407872).
>DBCC results for 'spt_monitor'.
>There are 1 rows in 1 pages for object 'spt_monitor'.
>DBCC results for 'spt_values'.
>There are 730 rows in 7 pages for object 'spt_values'.
>DBCC results for 'spt_fallback_db'.
>There are 0 rows in 0 pages for object 'spt_fallback_db'.
>DBCC results for 'spt_fallback_dev'.
>There are 0 rows in 0 pages for object 'spt_fallback_dev'.
>DBCC results for 'spt_fallback_usg'.
>There are 0 rows in 0 pages for object 'spt_fallback_usg'.
>CHECKDB found 1 allocation errors and 0 consistency errors in table '(Objec
t
>ID 538976288)' (object ID 538976288).
>DBCC results for 'spt_provider_types'.
>There are 25 rows in 1 pages for object 'spt_provider_types'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table '(Objec
t
>ID 1111693545)' (object ID 1111693545).
>DBCC results for 'spt_datatype_info_ext'.
>There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
>DBCC results for 'MSreplication_options'.
>There are 2 rows in 1 pages for object 'MSreplication_options'.
>DBCC results for 'spt_datatype_info'.
>There are 36 rows in 1 pages for object 'spt_datatype_info'.
>DBCC results for 'spt_server_info'.
>There are 29 rows in 1 pages for object 'spt_server_info'.
>CHECKDB found 4 allocation errors and 6 consistency errors in database
>'master'.
>repair_allow_data_loss is the minimum repair level for the errors found by
>DBCC CHECKDB (master ).
>DBCC execution completed. If DBCC printed error messages, contact your
>system administrator.
>How can I correct these errors?|||Would there be anyway to fix it if we did not have a good copy of the backup
?
"Sue Hoegemeier" wrote:

> Before fixing it, you should check your hardware and look
> for issues with your disk subsystem. Check the event logs on
> the server and look for any other system errors that may
> have occurred around the same time.
> After fixing any hardware issues, then you would need to
> restore the last known good backup of the master database.
> -Sue
> On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
> <rleamey@.discussions.microsoft.com> wrote:
>
>|||Restoring is the best option. If that's not an option, you
can rebuild master using the rebuildm.exe
You can find more information on how to do this in the books
online topic: Rebuilding the master Database
-Sue
On Thu, 30 Mar 2006 05:09:02 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Would there be anyway to fix it if we did not have a good copy of the backu
p?
>"Sue Hoegemeier" wrote:
>

Error '8007007f' after upgrading to Windows Server 2003

After upgrading to Windows Server 2003, i receive Error '8007007f' when quer
ying the database, it says i have an error on this line. I am running SQL Se
rver 2000 with SP 3a
Specter.Open "Provider=SQLOLEDB;User ID=;Password=;Data Source=Excursion;Dat
aBase=AE;Integrated Security=SSPI"I had the same problem after upgrading to Windows 2003 Server. I called Mic
rosoft and here is the fix:
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a dat
abase or data component will result in a '8007007f' or "The specified proced
ure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's impo
rtant that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the oled
b32.dll file.
You can dowload the oledb32.dll file here: [url]http://www.promiseweb.com/oledb32.zip[/
url]
This is per Malcolm Stewart at Microsoft Developer Support

Error 7399 in Openquery. GetNextRow in Informix

When I execute a Select using Openquery against Informix, sometimes I receive the error below:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Informix][Informix ODBC Driver]Error in row.]
[OLE/DB provider returned message: sqlerrm(table_name)]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowset::GetNextRows returned 0x80004005: ].

I noticed that the error is occuring when an user is Updating/Deleting or Inserting data in the table at the same time.

Environment:
Windows 2K
SQL Server 2000 with SP 3a
SDK Client 2.81 for Informix
ODBC 3.81 for Informix

Informix 7.3 running on a Unix machineHi,

Do you found any solution about this case? I have the same problem as you. Please send me information if you have some, this will be a big help for me.

Thank you and best regards,
ThinkMan|||Hi Thinkman,

Sorry, but I didnt find any solution for OUR problem.

Norivalsql

Error 7102

After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:

> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Erro
r
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern
,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would you
r
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 7102

After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Error 7102

After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.
Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:

> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Error -2147467259 upgrading SQL 6.5 to SQL 2000

I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
and I receive the following error from the Upgrade Wizard:
Export Exit Code: -2147467259 -
c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
-DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
-DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
****
Time:09-02-2004 17:55:13.272
Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
****Time : 09-02-2004 17:55:13
An Error occured while exporting table ACCOUNT
Time : 09-02-2004 17:55:13
An Error occured while exporting database AAP
Time : 09-02-2004 17:55:13
An error occured while importing table. Please check the error file.
Time : 09-02-2004 17:55:14
pSql65Server->DumpAllTables () failed. hr=-2147467259
Both SQL Server versions are on the same computer and I log on as a
domain administrator. Also, both SQL services start as Administrator.
DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
Any suggestions?
Thanks everyone.
Don't knkow how the upgrade wizard works but it looks like it is bcping the
data out and getting an error. Maybe running out of space?
"Leandro Ordo?ez" wrote:

> I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
> and I receive the following error from the Upgrade Wizard:
> Export Exit Code: -2147467259 -
> c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
> -DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
> -DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
> ****
> Time:09-02-2004 17:55:13.272
> Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
> ****Time : 09-02-2004 17:55:13
> An Error occured while exporting table ACCOUNT
> Time : 09-02-2004 17:55:13
> An Error occured while exporting database AAP
> Time : 09-02-2004 17:55:13
> An error occured while importing table. Please check the error file.
> Time : 09-02-2004 17:55:14
> pSql65Server->DumpAllTables () failed. hr=-2147467259
> Both SQL Server versions are on the same computer and I log on as a
> domain administrator. Also, both SQL services start as Administrator.
> DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
> Any suggestions?
> Thanks everyone.
>

Error -2147467259 upgrading SQL 6.5 to SQL 2000

I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
and I receive the following error from the Upgrade Wizard:
Export Exit Code: -2147467259 -
c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
-DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
-DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
****
Time:09-02-2004 17:55:13.272
Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
****Time : 09-02-2004 17:55:13
An Error occured while exporting table ACCOUNT
Time : 09-02-2004 17:55:13
An Error occured while exporting database AAP
Time : 09-02-2004 17:55:13
An error occured while importing table. Please check the error file.
Time : 09-02-2004 17:55:14
pSql65Server->DumpAllTables () failed. hr=-2147467259
Both SQL Server versions are on the same computer and I log on as a
domain administrator. Also, both SQL services start as Administrator.
DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
Any suggestions?
Thanks everyone.Don't knkow how the upgrade wizard works but it looks like it is bcping the
data out and getting an error. Maybe running out of space?
"Leandro Ordo?ez" wrote:
> I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
> and I receive the following error from the Upgrade Wizard:
> Export Exit Code: -2147467259 -
> c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
> -DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
> -DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
> ****
> Time:09-02-2004 17:55:13.272
> Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
> ****Time : 09-02-2004 17:55:13
> An Error occured while exporting table ACCOUNT
> Time : 09-02-2004 17:55:13
> An Error occured while exporting database AAP
> Time : 09-02-2004 17:55:13
> An error occured while importing table. Please check the error file.
> Time : 09-02-2004 17:55:14
> pSql65Server->DumpAllTables () failed. hr=-2147467259
> Both SQL Server versions are on the same computer and I log on as a
> domain administrator. Also, both SQL services start as Administrator.
> DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
> Any suggestions?
> Thanks everyone.
>

Error 208 Event ID 17052

Here is a weird one:
Using EM 2000 to connect to a 7.0 SQL Server. As soon as
I click on Management, I receive an error in my SQL Log
and Event Viewer for Error 208, Event ID 17052 stating
Invalid Object Name 'msdb.dbo.log_shipping_provider'
I do not have log shipping configured on any of my
servers. Has anyone ran into this'
Thanks!Here is some more interesting info:
This only happens when using EM 2000, if I use the 7.0 EM
it does not cause the error. Anyone connecting with EM
2000 can make the error occur. Any thoughts'
>--Original Message--
>Here is a weird one:
>Using EM 2000 to connect to a 7.0 SQL Server. As soon as
>I click on Management, I receive an error in my SQL Log
>and Event Viewer for Error 208, Event ID 17052 stating
>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>I do not have log shipping configured on any of my
>servers. Has anyone ran into this'
>Thanks!
>.
>|||Hi,
This error is generally caused if the object ownership is
not properly referenced when accessing that object. You
have to use the fully qualified name i.e
dbname.ObjectOwner.ObjectName.
It seems to me that the owner of
the 'log_shipping_provider' table in the msdb is NOT dbo.
You might want to take a look the ownership of this table.
Also, it is possible that the user connecting SQL Server 7
EM is connecting with the ID that owns that table!
Suppose the above table is owned id 'test'. You could be
trying to connected with 'sa' and the connection will
fail. But if you connect with 'test', it will work fine.
Take a look. hth
DeeJay
>--Original Message--
>Here is some more interesting info:
>This only happens when using EM 2000, if I use the 7.0 EM
>it does not cause the error. Anyone connecting with EM
>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>.
>|||The log shipping tables do not exist in 7.0
So ownership wasn't the prob.
>--Original Message--
>Hi,
>This error is generally caused if the object ownership is
>not properly referenced when accessing that object. You
>have to use the fully qualified name i.e
>dbname.ObjectOwner.ObjectName.
>It seems to me that the owner of
>the 'log_shipping_provider' table in the msdb is NOT dbo.
>You might want to take a look the ownership of this table.
>Also, it is possible that the user connecting SQL Server
7
>EM is connecting with the ID that owns that table!
>Suppose the above table is owned id 'test'. You could be
>trying to connected with 'sa' and the connection will
>fail. But if you connect with 'test', it will work fine.
>Take a look. hth
>DeeJay
>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>.
>|||Silly me ... I knew that!
Are you connecting through just the client Tools (from
your workstation) or from a machine where SQL Server
2000/7 is installed?
Eventhough, log shipping is not configured, this table
could still, somehow, exist. You might want to take look
at the msdb database.
I have not found anything else for this error.
hth
DeeJay
>--Original Message--
>The log shipping tables do not exist in 7.0
>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
dbo.
>>You might want to take a look the ownership of this
table.
>>Also, it is possible that the user connecting SQL Server
>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>>as
>>I click on Management, I receive an error in my SQL
Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>.
>|||I'm just connecting through the client tools. I've
checked msdb and haven't found anything that remotely
looks like the log shipping tables.
This is weird!
>--Original Message--
>Silly me ... I knew that!
>Are you connecting through just the client Tools (from
>your workstation) or from a machine where SQL Server
>2000/7 is installed?
>Eventhough, log shipping is not configured, this table
>could still, somehow, exist. You might want to take look
>at the msdb database.
>I have not found anything else for this error.
>hth
>DeeJay
>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>dbo.
>>You might want to take a look the ownership of this
>table.
>>Also, it is possible that the user connecting SQL
Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>>EM
>>it does not cause the error. Anyone connecting with
EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
soon
>>as
>>I click on Management, I receive an error in my SQL
>Log
>>and Event Viewer for Error 208, Event ID 17052
stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>.
>|||Hum...this one got me.
The only documentation for error 208 is for what we have
already talked about
>--Original Message--
>I'm just connecting through the client tools. I've
>checked msdb and haven't found anything that remotely
>looks like the log shipping tables.
>This is weird!
>>--Original Message--
>>Silly me ... I knew that!
>>Are you connecting through just the client Tools (from
>>your workstation) or from a machine where SQL Server
>>2000/7 is installed?
>>Eventhough, log shipping is not configured, this table
>>could still, somehow, exist. You might want to take look
>>at the msdb database.
>>I have not found anything else for this error.
>>hth
>>DeeJay
>>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>>is
>>not properly referenced when accessing that object.
You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>>dbo.
>>You might want to take a look the ownership of this
>>table.
>>Also, it is possible that the user connecting SQL
>Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
>be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work
fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the
7.0
>>EM
>>it does not cause the error. Anyone connecting with
>EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
>soon
>>as
>>I click on Management, I receive an error in my SQL
>>Log
>>and Event Viewer for Error 208, Event ID 17052
>stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>>.
>.
>

Error 195 from withing Ent Mgr

From SQL 2000 Ent Ed. sp3
When I try to view permissions via the enterrpise mgr for any object from
any database on this server I receive the following error:
<title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
<msg>= Error 195: 'schema_name' is not a recognized function name.
Research I googled relates to mal-formed queries or 3rd party software as
the cause. Any ideas...?
Thanks in advance,
ScottOne more thing...
I just found out that MS Operations Management Agent was installed (w/out my
knowledge). Could this be the cause?
"Scott O'Donnell" wrote:
> From SQL 2000 Ent Ed. sp3
> When I try to view permissions via the enterrpise mgr for any object from
> any database on this server I receive the following error:
> <title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
> <msg>= Error 195: 'schema_name' is not a recognized function name.
> Research I googled relates to mal-formed queries or 3rd party software as
> the cause. Any ideas...?
> Thanks in advance,
> Scott|||i have this problem:
when i execute this
SqlCommand mCmd = new SqlCommand( sQry,mConn );
mCmd.CommandType = System.Data.CommandType.Text;
mCmd.ExecuteNonQuery();
where sQry = "UPDATE StoreOperation SET Data=DateAdd(HH,FreqOra,DataAdd(
d,FreqData,Data )) WHERE IDStoreOperation=1"
i have this error message
"DateAdd is not a recognized function name"
in C++ the same sQry work fine. in .NET no.

Error 195 from withing Ent Mgr

From SQL 2000 Ent Ed. sp3
When I try to view permissions via the enterrpise mgr for any object from
any database on this server I receive the following error:
<title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
<msg>= Error 195: 'schema_name' is not a recognized function name.
Research I googled relates to mal-formed queries or 3rd party software as
the cause. Any ideas...?
Thanks in advance,
ScottOne more thing...
I just found out that MS Operations Management Agent was installed (w/out my
knowledge). Could this be the cause?
"Scott O'Donnell" wrote:

> From SQL 2000 Ent Ed. sp3
> When I try to view permissions via the enterrpise mgr for any object from
> any database on this server I receive the following error:
> <title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
> <msg>= Error 195: 'schema_name' is not a recognized function name.
> Research I googled relates to mal-formed queries or 3rd party software as
> the cause. Any ideas...?
> Thanks in advance,
> Scott|||i have this problem:
when i execute this
SqlCommand mCmd = new SqlCommand( sQry,mConn );
mCmd.CommandType = System.Data.CommandType.Text;
mCmd.ExecuteNonQuery();
where sQry = "UPDATE StoreOperation SET Data=DateAdd(HH,FreqOra,DataAdd(
d,FreqData,Data )) WHERE IDStoreOperation=1"
i have this error message
"DateAdd is not a recognized function name"
in C++ the same sQry work fine. in .NET no.

Error 195 from withing Ent Mgr

From SQL 2000 Ent Ed. sp3
When I try to view permissions via the enterrpise mgr for any object from
any database on this server I receive the following error:
<title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
<msg>= Error 195: 'schema_name' is not a recognized function name.
Research I googled relates to mal-formed queries or 3rd party software as
the cause. Any ideas...?
Thanks in advance,
Scott
One more thing...
I just found out that MS Operations Management Agent was installed (w/out my
knowledge). Could this be the cause?
"Scott O'Donnell" wrote:

> From SQL 2000 Ent Ed. sp3
> When I try to view permissions via the enterrpise mgr for any object from
> any database on this server I receive the following error:
> <title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
> <msg>= Error 195: 'schema_name' is not a recognized function name.
> Research I googled relates to mal-formed queries or 3rd party software as
> the cause. Any ideas...?
> Thanks in advance,
> Scott
|||i have this problem:
when i execute this
SqlCommand mCmd = new SqlCommand( sQry,mConn );
mCmd.CommandType = System.Data.CommandType.Text;
mCmd.ExecuteNonQuery();
where sQry = "UPDATE StoreOperation SET Data=DateAdd(HH,FreqOra,DataAdd(
d,FreqData,Data )) WHERE IDStoreOperation=1"
i have this error message
"DateAdd is not a recognized function name"
in C++ the same sQry work fine. in .NET no.

error 193 installing .net framework 2.0

Hi,
I'm trying to install SQL Server 2005 and I receive the "error 193 installing .net framework 2.0"
I got the same error when try to install the 32 bits SQL Server 2005 SE which I downloaded from MSDN. I got the same error even after I tried to install .Net Framework separately.
I tried the Developer Edition and there is no such error.

Is there something special with the SE CD?|||Hi,

what I did:

1.) Disabled the extended IE security on the Win2K3 server (saw that on another post)
2.) Installed .net Framework 2.0 from Windows Update
3.) Reboot

After that everything worked fine... No idea which of the 3 did the trick...|||Update:

No, it didn't work... I got the error message that IIS wasn't completely configured... I forgot to do so... After adding ASP.net to IIS the setup wants to install .net 2.0 again. No idea why. Even repairing the .net installation didn't help.
What I noticed is that all the graphics in the pre-setup screens are missing... Perhaps this has something to do with that...|||Are you using virtual machines? I am using VMware and found that my problem is an corrupted iso file. MY problem was resolved after I recreate the iso file.

So the error may be due to a bad installation media.|||How to disable the extended IE security on the Win2k3 server|||I thought disabling Extended IE Security would help (see my earlier post) but it didn't. It was a Virtual PC, I finally got it running not by using Developer Edition but Enterprise Edition... I also did a new download of the software (from MSDN) because I wasn't able to read the complete disk from the image. But that didn't help... My guess is a problem with VirtualPC... But I'm not sure...|||

I was trying to install SQL 2005 Developer edition to winXP sp2 on a virtual machine and got the same error. THen I downloaded framework 2 from win update and got the same error. Now I setup a virtual pc with Server 2003 enterprise sp1 disabled IE extended security and got the same error. So it might not be the problem (it is logical as ie on XP doesn;t have extended security).Right now I am updating that Virtual PC (server 2003 enterprise) with framework 2 . I'll reboot it and if that doesn't work I;ll change profession!!

It doesn't work still! I also get the problem where the graphics are not displayed like if an ActiveX control is missing.

|||Hi everybody, too many boys now angry with this problem.. and too many versions of this problem

this is mine:

1. i have.net framework 2.0 and i haveMs visual studio 2005 .
2. i tried to installMs SQL server 2005 Developer edition.
in first step [Server components, tools, Books Online, and samples] the installation sayas that net FRM 2.0 and support files required.
3. i click the install button and wow!! "error 193 installation Net Framework 2.0."
i cant understand, i havenet framework 2.0 and it cant install it. :S

i uninstalled all visual studio 2005 and net framework 2.0 and all other sql services.

and the same problem appears again.

Note: i run the installation program from full DVD [includes x86 x64 and itanium]

and no servers are running while installations.
i closed antivirus and firewall programmes while installation.
but the same error - that damned "error 193"

and please help me, and feel good to help a good boy :)
|||

If the install media is not a problem. How about trying to clean up the registry settings created by SQL2005.

Uninstall .net framwork 2.0 and also makie sure that your settings for the tmp folder is correct, clean up the temp and tmp folders

|||Map the DVD to a mapped drive in the virtual machine, ie the DVD is in the host OS, not in the VM. Run the setup.exe from the mapped drive. All is well after that.|||

ya boys.... thanks everybody.. and Yo123 thaks..

it is fine now.

let me say what i did:

1. i copy the full DVD to my local computer. like this --> c:\sql_detup_files

2. then i uninstalled the sql server and all components

3. and... try again to install sql server -- correct the instance names bla bla

4. then everything ok.

|||

I believe your installation file was corrupted:

Please check if the file is corrupted in SQL2005\redist\2.0\dotnetfx.exe

|||I also had the same issue and running a repair on .net 2.0 fixed it.

error 193 installing .net framework 2.0

Hi,
I'm trying to install SQL Server 2005 and I receive the "error 193 installing .net framework 2.0"
I got the same error when try to install the 32 bits SQL Server 2005 SE which I downloaded from MSDN. I got the same error even after I tried to install .Net Framework separately.
I tried the Developer Edition and there is no such error.

Is there something special with the SE CD?|||Hi,

what I did:

1.) Disabled the extended IE security on the Win2K3 server (saw that on another post)
2.) Installed .net Framework 2.0 from Windows Update
3.) Reboot

After that everything worked fine... No idea which of the 3 did the trick...|||Update:

No, it didn't work... I got the error message that IIS wasn't completely configured... I forgot to do so... After adding ASP.net to IIS the setup wants to install .net 2.0 again. No idea why. Even repairing the .net installation didn't help.
What I noticed is that all the graphics in the pre-setup screens are missing... Perhaps this has something to do with that...|||Are you using virtual machines? I am using VMware and found that my problem is an corrupted iso file. MY problem was resolved after I recreate the iso file.

So the error may be due to a bad installation media.|||How to disable the extended IE security on the Win2k3 server|||I thought disabling Extended IE Security would help (see my earlier post) but it didn't. It was a Virtual PC, I finally got it running not by using Developer Edition but Enterprise Edition... I also did a new download of the software (from MSDN) because I wasn't able to read the complete disk from the image. But that didn't help... My guess is a problem with VirtualPC... But I'm not sure...|||

I was trying to install SQL 2005 Developer edition to winXP sp2 on a virtual machine and got the same error. THen I downloaded framework 2 from win update and got the same error. Now I setup a virtual pc with Server 2003 enterprise sp1 disabled IE extended security and got the same error. So it might not be the problem (it is logical as ie on XP doesn;t have extended security).Right now I am updating that Virtual PC (server 2003 enterprise) with framework 2 . I'll reboot it and if that doesn't work I;ll change profession!!

It doesn't work still! I also get the problem where the graphics are not displayed like if an ActiveX control is missing.

|||Hi everybody, too many boys now angry with this problem.. and too many versions of this problem

this is mine:

1. i have .net framework 2.0 and i have Ms visual studio 2005 .
2. i tried to install Ms SQL server 2005 Developer edition.
in

first step [Server components, tools, Books Online, and samples] the

installation sayas that net FRM 2.0 and support files required.
3. i click the install button and wow!! "error 193 installation Net Framework 2.0."
i cant understand, i have net framework 2.0 and it cant install it. :S

i uninstalled all visual studio 2005 and net framework 2.0 and all other sql services.

and the same problem appears again.

Note: i run the installation program from full DVD [includes x86 x64 and itanium]

and no servers are running while installations.
i closed antivirus and firewall programmes while installation.
but the same error - that damned "error 193"

and please help me, and feel good to help a good boy :)
|||

If the install media is not a problem. How about trying to clean up the registry settings created by SQL2005.

Uninstall .net framwork 2.0 and also makie sure that your settings for the tmp folder is correct, clean up the temp and tmp folders

|||Map the DVD to a mapped drive in the virtual machine, ie the DVD is in the host OS, not in the VM. Run the setup.exe from the mapped drive. All is well after that.|||

ya boys.... thanks everybody.. and Yo123 thaks..

it is fine now.

let me say what i did:

1. i copy the full DVD to my local computer. like this --> c:\sql_detup_files

2. then i uninstalled the sql server and all components

3. and... try again to install sql server -- correct the instance names bla bla

4. then everything ok.

|||

I believe your installation file was corrupted:

Please check if the file is corrupted in SQL2005\redist\2.0\dotnetfx.exe

error 193 installing .net framework 2.0

Hi,
I'm trying to install SQL Server 2005 and I receive the "error 193 installing .net framework 2.0"
I got the same error when try to install the 32 bits SQL Server 2005 SE which I downloaded from MSDN. I got the same error even after I tried to install .Net Framework separately.
I tried the Developer Edition and there is no such error.

Is there something special with the SE CD?|||Hi,

what I did:

1.) Disabled the extended IE security on the Win2K3 server (saw that on another post)
2.) Installed .net Framework 2.0 from Windows Update
3.) Reboot

After that everything worked fine... No idea which of the 3 did the trick...|||Update:

No, it didn't work... I got the error message that IIS wasn't completely configured... I forgot to do so... After adding ASP.net to IIS the setup wants to install .net 2.0 again. No idea why. Even repairing the .net installation didn't help.
What I noticed is that all the graphics in the pre-setup screens are missing... Perhaps this has something to do with that...|||Are you using virtual machines? I am using VMware and found that my problem is an corrupted iso file. MY problem was resolved after I recreate the iso file.

So the error may be due to a bad installation media.|||How to disable the extended IE security on the Win2k3 server|||I thought disabling Extended IE Security would help (see my earlier post) but it didn't. It was a Virtual PC, I finally got it running not by using Developer Edition but Enterprise Edition... I also did a new download of the software (from MSDN) because I wasn't able to read the complete disk from the image. But that didn't help... My guess is a problem with VirtualPC... But I'm not sure...|||

I was trying to install SQL 2005 Developer edition to winXP sp2 on a virtual machine and got the same error. THen I downloaded framework 2 from win update and got the same error. Now I setup a virtual pc with Server 2003 enterprise sp1 disabled IE extended security and got the same error. So it might not be the problem (it is logical as ie on XP doesn;t have extended security).Right now I am updating that Virtual PC (server 2003 enterprise) with framework 2 . I'll reboot it and if that doesn't work I;ll change profession!!

It doesn't work still! I also get the problem where the graphics are not displayed like if an ActiveX control is missing.

|||Hi everybody, too many boys now angry with this problem.. and too many versions of this problem

this is mine:

1. i have.net framework 2.0 and i haveMs visual studio 2005 .
2. i tried to installMs SQL server 2005 Developer edition.
in first step [Server components, tools, Books Online, and samples] the installation sayas that net FRM 2.0 and support files required.
3. i click the install button and wow!! "error 193 installation Net Framework 2.0."
i cant understand, i havenet framework 2.0 and it cant install it. :S

i uninstalled all visual studio 2005 and net framework 2.0 and all other sql services.

and the same problem appears again.

Note: i run the installation program from full DVD [includes x86 x64 and itanium]

and no servers are running while installations.
i closed antivirus and firewall programmes while installation.
but the same error - that damned "error 193"

and please help me, and feel good to help a good boy :)
|||

If the install media is not a problem. How about trying to clean up the registry settings created by SQL2005.

Uninstall .net framwork 2.0 and also makie sure that your settings for the tmp folder is correct, clean up the temp and tmp folders

|||Map the DVD to a mapped drive in the virtual machine, ie the DVD is in the host OS, not in the VM. Run the setup.exe from the mapped drive. All is well after that.|||

ya boys.... thanks everybody.. and Yo123 thaks..

it is fine now.

let me say what i did:

1. i copy the full DVD to my local computer. like this --> c:\sql_detup_files

2. then i uninstalled the sql server and all components

3. and... try again to install sql server -- correct the instance names bla bla

4. then everything ok.

|||

I believe your installation file was corrupted:

Please check if the file is corrupted in SQL2005\redist\2.0\dotnetfx.exe

|||I also had the same issue and running a repair on .net 2.0 fixed it.