FIX: An Internet Explorer script error occurs when you access metadata information by using DTS in SQL Server Enterprise Manager

Article translations Article translations
Article ID: 828308 - View products that this article applies to.
Bug #: 470167 (SQL Server 8.0)
Microsoft SQL Server 2000 fixes are distributed as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included in the previous SQL Server 2000 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to access the metadata information for a table or a column by using Data Transformation Services (DTS) in SQL Server Enterprise Manager, you may receive a Microsoft Internet Explorer script error message that is similar to the following:
Cannot use parentheses when calling a Sub
This problem may occur if Internet Explorer 6.0 or later is installed on your computer.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   ---------------------------------------------------------------------
   31-May-2003  06:15  2000.80.818.0      78,400  Console.exe      
   24-Jun-2003  12:31  2000.80.818.0      33,340  Dbmslpcn.dll     
   24-Apr-2003  13:42                    786,432  Distmdl.ldf
   24-Apr-2003  13:42                  2,359,296  Distmdl.mdf
   29-Jan-2003  13:25                        180  Drop_repl_hotfix.sql
   26-Aug-2003  07:46  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  10:10  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  10:10  2000.80.837.0     639,552  Dtswiz.dll       
   23-Apr-2003  14:21                    747,927  Instdist.sql
   02-May-2003  13:26                      1,581  Inst_repl_hotfix.sql
   07-Feb-2003  18:10  2000.80.765.0      90,692  Msgprox.dll      
   31-Mar-2003  13:37                      1,873  Odsole.sql
   04-Apr-2003  13:16  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  08:11  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  09:18  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  10:45  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  05:47                    550,780  Procsyst.sql
   22-May-2003  10:27                     19,195  Qfe469571.sql
   11-Jul-2003  04:34                  1,084,147  Replmerg.sql
   04-Apr-2003  09:23  2000.80.798.0     221,768  Replprov.dll     
   07-Feb-2003  18:10  2000.80.765.0     307,784  Replrec.dll      
   13-Aug-2003  03:58                  1,086,797  Replsys.sql
   13-Aug-2003  03:58                    986,603  Repltran.sql
   29-Jul-2003  07:43  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  05:57  2000.80.818.0     172,032  Semobj.rll
   05-Aug-2003  08:36                    127,884  Sp3_serv_uni.sql
   31-May-2003  12:31  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  05:14                     25,172  Sqldumper.exe    
   19-Mar-2003  05:50  2000.80.789.0      28,672  Sqlevn70.rll
   01-Jul-2003  11:48  2000.80.834.0     180,736  Sqlmap70.dll     
   02-Sep-2003  14:26  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  10:33  2000.80.857.0     479,232  Sqlmmc.rll
   07-Feb-2003  18:10  2000.80.765.0      57,920  Sqlrepss.dll     
   02-Sep-2003  14:27  2000.80.857.0   7,598,161  Sqlservr.exe     
   25-Jul-2003  09:14  2000.80.845.0     590,396  Sqlsort.dll      
   07-Feb-2003  18:10  2000.80.765.0      45,644  Sqlvdi.dll       
   24-Jun-2003  12:31  2000.80.818.0      33,340  Ssmslpcn.dll     
   31-May-2003  12:31  2000.80.818.0      82,492  Ssnetlib.dll     
   31-May-2003  12:31  2000.80.818.0      25,148  Ssnmpn70.dll     
   31-May-2003  12:31  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  06:29  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  11:22  2000.80.816.0      45,132  Ums.dll          
   01-Jul-2003  11:49  2000.80.834.0      98,816  Xpweb70.dll 
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

To work around this problem, use one of the following methods:
  • Use the sp_addextendedproperty system stored procedure to update the metadata information for the objects. For more information about the sp_addextendedproperty system stored procedure, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/aa259572(SQL.80).aspx
  • Run Meta Data Services as a stand-alone Microsoft Management Console (MMC) snap-in, and then use Meta Data Browser to view or to update the metadata information for the objects. To access the metadata information, you must register the SQL Server msdb system database in Meta Data Browser. The msdb system database contains the repository tables to support the management and storage of SQL Server metadata. For more information about using Meta Data Browser, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/aa972302(SQL.80).aspx

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

MORE INFORMATION

Steps to Reproduce the Problem

To reproduce the problem, follow these steps:
  1. Start SQL Server Enterprise Manager.
  2. In the left pane, expand the node that corresponds to the instance of SQL Server, and then expand Data Transformation Services.
  3. Right-click Meta Data, and then click Import Metadata.
  4. In the Connection Properties dialog box, click an appropriate data source in the Data Source list.
  5. Specify the server name, the authentication method, and the database that you want to connect to the data source.
  6. Click OK.

    Note You may notice that the metadata information is imported and displayed in the right pane.
  7. In the right pane, expand the database name, and then expand the database owner name.
  8. In the list of tables that appears under the database owner name, click a table name.

    You may receive the Internet Explorer script error message.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Properties

Article ID: 828308 - Last Review: November 2, 2007 - Revision: 3.5
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
  • Microsoft Internet Explorer 6.0
Keywords: 
kbhotfixserver kbqfe kbqfe kbscript kbdatabase kbsnapin kberrmsg kbsqlserv2000presp4fix kbfix kbbug KB828308

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com