| Message ID | Severity | Message |
|---|---|---|
|
9029 |
Error |
An error was encountered while a database statement handle was being allocated (Inter-site Configuration Management). |
|
9030 |
Error |
No software metering configuration information was found in the site control file (Table=%1, Option=%2). |
|
9031 |
Error |
An error was encountered while the software metering configuration database was being updated (SQL=%1). |
|
9032 |
Error |
An unknown error was encountered while the software metering configuration was trying to update. |
|
9033 |
Error |
An error was encountered while the software metering configuration information from the site control file was being read. |
|
9034 |
Error |
An error was encountered while the software metering database was trying to open (DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9035 |
Error |
An error was encountered while the %1 software metering configuration table was updating (DSN=%2). |
|
9036 |
Error |
An error was encountered while collation data was being sent. |
|
9037 |
Error |
An error was encountered while collation data was being gathered. |
|
9038 |
Error |
An error was encountered while a data rollback was being attempted. |
|
9039 |
Error |
An error was encountered while data was being accepted. |
|
9040 |
Error |
An error was encountered while the application attempted to read a table. |
|
9041 |
Error |
The data to be inserted into the %1 table is in the wrong format. |
|
9042 |
Error |
An error was encountered while the application attempted to write to table %1. |
|
9043 |
Error |
An error was encountered while the application attempted to roll back %1 with the index %2. |
|
9044 |
Error |
An error was encountered while the application attempted to commit the %1 table with index %2. |
|
9045 |
Error |
An error was encountered while the application attempted to get a computer ID from the %1 table for computer %2. |
|
9046 |
Error |
An error was encountered while the application was attempting to get a user ID from the %1 table for user %2. |
|
9047 |
Error |
An error was encountered while the application was attempting to get the next CollRun value for %1. |
|
9048 |
Error |
An error was encountered while the application was attempting to flag the %1 table. |
|
9049 |
Error |
An error was encountered while the application was attempting to add data to the ABCGRANT table. |
|
9050 |
Error |
An error was encountered while the application was attempting to get data from the ABCGRANT table (flagged with: %1). |
|
9051 |
Error |
An error was encountered while the application was attempting to add data to the NONLIC table. |
|
9052 |
Error |
An error was encountered while the application was attempting to get data from the NONLIC table (flagged with: %1). |
|
9053 |
Error |
An error was encountered while the application was attempting to add data to the AUDIT table. |
|
9054 |
Error |
An error was encountered while the application was attempting to get data from the AUDIT table (flagged with: %1). |
|
9055 |
Error |
An error was encountered while the application was attempting to add data to the DENIAL table. |
|
9056 |
Error |
An error was encountered while the application was attempting to get data from the DENIAL table (flagged with: %1). |
|
9057 |
Error |
An error was encountered while the application was collating data from local software metering servers. |
|
9058 |
Error |
An unknown database type was detected in the table ABCSVRCG. |
|
9059 |
Error |
Could not enumerate local software metering servers. |
|
9060 |
Error |
A database error was encountered while the application was collating data from a software metering server (SQL=%1). |
|
9061 |
Error |
An unknown error was encountered while the application was collating data from a software metering server. |
|
9062 |
Error |
A database problem was encountered while the application was initializing the software metering databases (SQL=%1). |
|
9063 |
Error |
An unknown error was encountered while the application was initializing the software metering databases. |
|
9064 |
Error |
A database problem was encountered while the application was rolling back the software metering databases (SQL=%1). |
|
9065 |
Error |
An unknown error was encountered while the application was rolling back the software metering databases. |
|
9066 |
Error |
A database problem was encountered while the application was transferring data (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9067 |
Error |
An unknown problem was encountered while the application was transferring data. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9068 |
Error |
A database problem was encountered while the application was committing records to the site server (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9069 |
Error |
An unknown error was encountered while the application was committing records to the site server. |
|
9070 |
Error |
A database problem was encountered while the application was purging records from the site server (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9071 |
Error |
An unknown error was encountered while the application was purging records from the site server. |
|
9072 |
Error |
The site server database field was not found in the software metering server database. |
|
9073 |
Error |
The lCollRun field was not found in the site server database. |
|
9074 |
Error |
The lUserRef field was not found in the site server database. |
|
9075 |
Error |
The lWksnRef field was not found in the site server database. |
|
9076 |
Error |
The software metering server database field was not found in the site server database. |
|
9077 |
Error |
The lCollRun field was not found in the software metering server database. |
|
9078 |
Error |
The lUserRef field was not found in the software metering server database. |
|
9079 |
Error |
The lWksnRef field was not found in software metering server database. |
|
9080 |
Error |
A database problem was encountered while the application was flagging ABCGRANT records (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9081 |
Error |
An unknown problem was encountered while the application was flagging ABCGRANT records. |
|
9082 |
Error |
A database problem was encountered while the application was flagging NONLIC records (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9083 |
Error |
An unknown problem was encountered while the application was flagging NONLIC records. |
|
9084 |
Error |
A database problem was encountered while the application was flagging AUDIT records (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9085 |
Error |
An unknown problem was encountered while the application was flagging AUDIT records. |
|
9086 |
Error |
A database problem was encountered while the application was flagging DENIAL records (SQL=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9087 |
Error |
An unknown problem was encountered while the application was flagging DENIAL records. |
|
9088 |
Error |
An error was encountered while the application was summarizing data. |
|
9089 |
Error |
There was a problem connecting to %1 database. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9090 |
Error |
An error was encountered while the application was summarizing data. |
|
9091 |
Error |
A problem was encountered while disconnecting from the database. |
|
9092 |
Error |
A problem was encountered while the application was exiting the program. |
|
9093 |
Error |
A problem was encountered while the application was exiting the program. |
|
9094 |
Error |
The application could not calculate the use of licensed product %1 version %2 (%3, %4, %5, %6). |
|
9095 |
Error |
The application could not summarize the use of licensed product %1 version %2 (%3, %4, %5, %6). |
|
9096 |
Error |
The application could not remove the unsummarized use of licensed product %1 version %2 (%3, %4, %5, %6). |
|
9097 |
Error |
The application could not update the summarized use of licensed product %1 version %2 (%3, %4, %5, %6). |
|
9098 |
Error |
A problem was encountered while the application was exiting the program. |
|
9099 |
Error |
The application could not calculate the use of unlicensed product %1 version %2 (%3, %4, %5, %6). |
|
9100 |
Error |
The application could not summarize the use of unlicensed product %1 version %2 (%3, %4, %5, %6). |
|
9101 |
Error |
The application could not remove the unsummarized use of unlicensed product %1 version %2 (%3, %4, %5, %6). |
|
9102 |
Error |
The application could not update the summarized use of unlicensed product %1 version %2 (%3, %4, %5, %6). |
|
9103 |
Error |
The application could not initialize local license balancing (DSN=%1). |
|
9104 |
Error |
An error was encountered while the application was performing local license balancing (DSN=%1). |
|
9105 |
Error |
An error was encountered while the application was performing instant local license balancing (DSN=%1). |
|
9106 |
Error |
Local license balancing could not initialize the software metering server by using the driver %1. |
|
9107 |
Warning |
Local license balancing has stopped until %1 license(s) of %2 (ProdRef=%3) are placed back into the software metering system. |
|
9108 |
Warning |
%1 licenses of %2 (ProdRef=%3) were removed from the software metering server %4 but could not be added to the site server on the Data Source Name %5. Add %1 licenses back into %4. Local license balancing is suspended until this is resolved. |
|
9109 |
Informational |
%1 number of surplus licenses of %2 (ProdRef=%3) were removed from the software metering server %4 and added to the license store at the site server (DSN=%5). |
|
9110 |
Error |
An unknown error was encountered while the application was giving licenses from software metering server %1 to the license store at the site server. |
|
9111 |
Warning |
%1 licenses of %2 (ProdRef=%3) were removed from the license store on the site server but could not be added to the software metering server %4. Add %1 licenses to %4. Local license balancing is suspended until this is resolved. |
|
9112 |
Informational |
%1 surplus licenses of %2 (ProdRef=%3) were removed from the license store at the site server and added to the software metering server %4. |
|
9113 |
Error |
An unknown error was encountered while the application was getting licenses from the license store at the site server to the software metering server %1. |
|
9114 |
Error |
An unknown database type was encountered while the application was obtaining the list of software metering servers. |
|
9115 |
Error |
An unknown error was encountered while the application was obtaining the list of software metering servers. |
|
9116 |
Error |
An unknown error was encountered while the application was obtaining the local license balancing settings. |
|
9117 |
Error |
An unknown error was encountered while the application was performing local license balancing. |
|
9118 |
Error |
An unknown error was encountered while the application was deinitializing the local license balancing service. |
|
9119 |
Error |
An unknown error was encountered while the local license balancing service was attaching to a database (DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9120 |
Error |
An unknown error was encountered while the application was adding %1 licenses of %2 to the server on DSN %3. |
|
9121 |
Error |
An unknown error was encountered while the application was removing %1 licenses of %2 from the server on Data Source Name %3. |
|
9122 |
Error |
An unknown error was encountered while the application was calculating the peak use for %1. |
|
9123 |
Error |
An unknown error was encountered while the application was calculating today’s peak use for %1. |
|
9124 |
Error |
An unknown error was encountered while the application was clearing the instant license balancing settings. |
|
9125 |
Error |
An unknown error was encountered while the application was checking whether or not a product requires instant license balancing (ProdRef=%1). |
|
9126 |
Error |
An error was encountered while the application was trying to remove entries for computers that are turned off. |
|
9127 |
Error |
An unknown error was encountered while the application was trying to remove computer entries at a software metering server for computers that are turned off (Temp DSN=%1). |
|
9128 |
Error |
An error was encountered while the application was trying to remove timed-out callbacks. |
|
9129 |
Error |
An unknown error was encountered while the application was trying to remove timed-out callbacks at a software metering server (Temp DSN=%1). |
|
9130 |
Error |
An error was encountered while the application was trying to remove old peak-use data. |
|
9131 |
Error |
An unknown error was encountered while the application was trying to remove old peak-use data at a software metering server (Temp DSN=%1). |
|
9132 |
Error |
An error was encountered while the application was trying to remove checked-out licenses that have expired. |
|
9133 |
Error |
An error was encountered while the application was trying to remove checked-out licenses that have expired at a software metering server (Temp DSN=%1). |
|
9134 |
Error |
An error was encountered while the application was trying to connect to the site server database (DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9135 |
Error |
A database error was encountered while the application was trying to connect to the site server database (DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9136 |
Error |
An unknown database field type was found in table %1. |
|
9137 |
Error |
A database error was encountered while the application was trying to obtain a list of software metering servers. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9138 |
Error |
An unknown error was encountered while the application was trying to obtain a list of software metering servers. |
|
9139 |
Error |
An unknown error was encountered while the application was trying to shut down site maintenance. |
|
9140 |
Error |
An error was encountered while the application was trying to return checked-in licenses to the correct software metering server. |
|
9141 |
Error |
An error was encountered while the application was obtaining a list of check-in servers stored on %1. |
|
9142 |
Error |
The application could not find a reference to the server %1 in the database. |
|
9143 |
Error |
The application could not return checked in licenses to %1. |
|
9144 |
Error |
An unknown error was encountered while the application was removing checked-in licenses from the Data Source Name %1. |
|
9145 |
Error |
An unknown error was encountered while the application was getting the list of software metering servers required to return checked-in licenses to (querying %1). |
|
9146 |
Error |
An error was encountered while the application was expiring products (DSN=%1). |
|
9147 |
Error |
A database error was encountered while the application was expiring products (DSN=%1, SQL=%2). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9148 |
Error |
An error was encountered while the application was deleting products (DSN=%1). |
|
9149 |
Error |
An error was encountered while the application was unlinking products (DSN=%1). |
|
9150 |
Error |
The application could not initialize site management on Data Source Name %1. |
|
9151 |
Error |
An error was encountered while the application was deleting a product (ProdRef=%1). |
|
9152 |
Error |
An error was encountered while the application was checking whether or not a product was live (ProdRef=%1). |
|
9153 |
Error |
An error was encountered while the application was checking whether or not a product is in a suite (ProdRef=%1). |
|
9154 |
Error |
An error was encountered while the application was unlinking a product from a suite (ProdRef=%1, SuiteRef=%2). |
|
9155 |
Error |
An error was encountered while the application was checking whether or not a product exists (ProdRef=%1). |
|
9156 |
Error |
An error was encountered while the application was checking whether or not a product (or suite) exists (ProdRef=%1, SuiteRef=%2). |
|
9157 |
Error |
An unknown error was encountered while the application was deinitializing site management. |
|
9158 |
Error |
An unknown error was encountered while the application was initializing site management (DSN=%1). |
|
9159 |
Error |
The application could not connect to site server (DSN=%1). |
|
9160 |
Error |
The application could not initialize software metering servers. |
|
9161 |
Error |
The application could not connect to the software metering servers. |
|
9162 |
Error |
An unknown error was encountered while the application was obtaining the list of software metering servers. |
|
9163 |
Error |
An unknown database type was found while obtaining the list of software metering servers. |
|
9164 |
Error |
An error was encountered while the application was initializing the site server (local config, DSN=%1). |
|
9165 |
Error |
An error was encountered while the application was performing local configuration (DSN=%1). |
|
9166 |
Error |
An error was encountered while the application was initializing the site server (intersite config, DSN=%1). |
|
9167 |
Error |
An error was encountered while the application was receiving tables for intersite table configuration (file=%1). |
|
9168 |
Error |
An error was encountered while the application was sending tables for intersite table configuration (child=%1, parent=%2). |
|
9169 |
Error |
An error was encountered while the application was connecting to the site server (intersite, DSN=%1). |
|
9170 |
Error |
A database error was encountered while the application was connecting to the site server (intersite, DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9171 |
Error |
An error was encountered while the application was connecting to the site server (local, DSN=%1). |
|
9172 |
Error |
A database error was encountered while the application was connecting to the site server (local, DSN=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9173 |
Error |
An unknown database was found in table %1. |
|
9174 |
Error |
A database error was encountered while the application was obtaining a list of software metering servers. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9175 |
Error |
An error was encountered while the application was obtaining a list of software metering servers. |
|
9176 |
Error |
An error was encountered while the application was receiving tables for intersite table configuration (file=%1). |
|
9177 |
Error |
A database error was encountered while the application was receiving tables for intersite table configuration (file=%1). |
|
9178 |
Error |
An error was encountered while the application was sending tables for intersite table configuration (child=%1, parent=%2). |
|
9179 |
Error |
A database error was encountered while the application was sending tables for intersite table configuration (child=%1, parent=%2). |
|
9180 |
Error |
An error was encountered while the application was performing local configuration (software metering server=%1). |
|
9181 |
Error |
A database error was encountered while the application was performing local configuration (software metering server=%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9182 |
Error |
A database error was encountered while the application was verifying if data from the site server is present at the software metering server (table=%1, field=%2, condition=%3). |
|
9183 |
Error |
An error was encountered while the application was verifying if data from the site server is present at the software metering server (table=%1, field=%2, condition=%3). |
|
9184 |
Error |
A database error was encountered while the application was inserting data from the site server into the software metering server (table=%1, insert=%2). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9185 |
Error |
An error was encountered while the application was inserting data from the site server into the software metering server (table=%1, insert=%2). Possible cause: Low disk space on the drive containing the file %1. Solution: Make some space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The file %1 exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. Possible cause: The file %1 exists, but it is corrupt. Solution: [component-specific]. If you ignore this problem, SMS will probably fix it and complete this operation later, but if this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
9186 |
Error |
A database error was encountered while the application was updating data from the site server to the software metering server (table=%1, update=%2). |
|
9187 |
Error |
An error was encountered while the application was updating data from the site server to the software metering server (table=%1, update=%2). |
|
9188 |
Informational |
The application is reading offline log %1. |
|
9189 |
Informational |
The application is matching license requests to available licenses (license start time to license end time). |
|
9190 |
Informational |
The application is looking for instances of product suites. |
|
9191 |
Informational |
The application is writing entries into the database. |
|
9192 |
Error |
An error was encountered while the application was reading the offline log %1. |
|
9193 |
Error |
An error was encountered while the application was matching license requests to available licenses (license start time to license end time). |
|
9194 |
Error |
An error was encountered while the application was looking for instances of product suites. |
|
9195 |
Error |
An error was encountered while the application was writing the entries into the database. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9196 |
Informational |
The licensed product %1 (version %2) is inactive on the computer %3 (user: %4, time: %5, software metering server: %6). |
|
9197 |
Informational |
The user %1 was denied access to %2 (version %3) on the computer %4 (time: %5, software metering server: %6). |
|
9198 |
Warning |
The software metering server %1 has a low number of licenses for product %2 (version %3) (time: %4). |
|
9199 |
Warning |
There are no more available licenses of %1 (version %2) on the software metering server %3 (time: %4). |
|
9200 |
Informational |
The software metering client on the computer %1 (user %2) is performing a normal shutdown (time: %3). |
|
9201 |
Error |
The software metering client on the computer %1 (user %2) could not recognize the drive type (time: %3). |
|
9202 |
Error |
The software metering client on the computer %1 (user %2) encountered an error and is performing an abnormal shut down (time: %3). |
|
9203 |
Warning |
The software metering client on the computer %1 (user %2) could not shut down %3 (time: %4). |
|
9204 |
Warning |
The software metering client on the computer %1 (user %2) cannot find any running processes (time: %3). |
|
9205 |
Informational |
Software metering has successfully configured the system registry for this site. |
|
9206 |
Error |
The software metering configuration service could not load the DLL %1. |
|
9207 |
Error |
The software metering configuration service could not write to the proposed site control file (%1). |
|
9208 |
Warning |
The software metering settings have not yet been accepted by the site configuration manager. Software metering will sleep until %1 (%2 seconds). |
|
9209 |
Warning |
The software metering settings were not accepted by the site configuration manager. Software metering will retry in %1 seconds. |
|
9210 |
Error |
The software metering settings were not accepted by the site configuration manager (after retrying %1 times). Software metering has not been configured correctly on this site. |
|
9211 |
Informational |
The software metering inbox (%1) has been successfully created. |
|
9212 |
Error |
Software metering could not create the software metering inbox %1. |
|
9213 |
Informational |
Software metering has been successfully configured on this site (%1). |
|
9214 |
Error |
An error was encountered while the application was configuring software metering on this site (%1). Software metering is disabled. |
|
9215 |
Error |
Software metering could not find the %1 ODBC driver. This driver is required for software metering. Only the following ODBC drivers are installed: %2 |
|
9216 |
Error |
ODBC has not been configured correctly on this site. ODBC is required for software metering. |
|
9217 |
Informational |
Software metering has configured ODBC correctly on this site. |
|
9218 |
Error |
ODBC would not add the Data Source Name (DSN) %1 (%2). Software metering requires this DSN. |
|
9219 |
Informational |
Software metering successfully added the ODBC Data Source Name (DSN) %1 (%2). |
|
9220 |
Informational |
The Inbox Manager has not yet created the software metering inbox. The service will retry in %1 seconds. |
|
9221 |
Error |
The software metering configuration component failed to set up the database. Software metering is not correctly configured on this site (%1). |
|
9222 |
Informational |
Software metering successfully configured the database on this site (%1). |
|
9223 |
Error |
An unknown error was encountered while the application was configuring the %1 table. |
|
9224 |
Error |
An unknown error was encountered while the application was configuring the software metering tables. |
|
9225 |
Error |
The software metering configuration component could not open the database for %1. Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9226 |
Error |
The software metering configuration component could not allocate a database statement handle. |
|
9227 |
Informational |
The application is initializing the Software Metering Server Manager. |
|
9228 |
Informational |
The application is deinitializing the Software Metering Server Manager. |
|
9229 |
Error |
An unknown error was encountered while the application was running the Software Metering Server Manager service. |
|
9230 |
Error |
The Software Metering Server Manager could not load the DLL %1. |
|
9231 |
Warning |
The application is stopping the Software Metering Server Manager after an abnormal condition. |
|
9232 |
Error |
The Software Metering Server Manager could not read the master site control file. |
|
9233 |
Informational |
The Software Metering Server Manager will process the following servers: |
|
9234 |
Error |
The Software Metering Server Manager could not write to a proposed site control file. |
|
9235 |
Warning |
The Software Metering Server Manager could not install the server %1. The installation will be retried. |
|
9236 |
Informational |
The Software Metering Server Manager successfully installed the server %1. |
|
9237 |
Error |
The Software Metering Server Manager could not upgrade the server %1. |
|
9238 |
Informational |
The Software Metering Server Manager successfully upgraded the server %1. |
|
9239 |
Error |
The Software Metering Server Manager could not configure the server %1. |
|
9240 |
Informational |
The Software Metering Server Manager successfully configured the server %1. |
|
9241 |
Error |
The Software Metering Server Manager could not deinstall the server %1. |
|
9242 |
Informational |
The Software Metering Server Manager successfully deinstalled the server %1. |
|
9243 |
Error |
An unknown error was encountered while the Software Metering Server Manager was attempting to install the server %1. |
|
9244 |
Warning |
The share %1 already exists on the server %2. This implies that a previous installation on this server failed or that another site is using %2 as a software metering server. The software metering server installation on %2 will be cancelled. If a previous installation has failed, you can remove the LicMtr share and directory on the server and let the Software Metering Server Manager retry the installation. |
|
9245 |
Error |
The Software Metering Server Manager could not create the share %1 for the directory %2 on the server %3. Possible cause: The Software Metering Server Manager’s account has insufficient privileges for this operation. Solution: Make sure that the Software Metering Server Manager’s account has sufficient privileges to create shares on %3. |
|
9246 |
Error |
The Software Metering Server Manager could not create the directory %1 on the server %2. Possible cause: The Software Metering Server Manager’s account has insufficient privileges for this operation. Solution: Make sure that the Software Metering Server Manager’s account has sufficient privileges to create directories on %2. |
|
9247 |
Error |
The Software Metering Server Manager could not attach to %1. Possible cause: %1 is not shared. Solution: Make sure that this is shared. Possible cause: The Service account does not have sufficient privileges for this operation. Solution: Make sure that the Service account has logon privileges. |
|
9248 |
Error |
The Software Metering Server Manager encountered an unknown error while installing ODBC on the server %1. The installation will be retried later. |
|
9249 |
Error |
The Software Metering Server Manager encountered an error while copying ODBC files to the System32 directory on the server %1. The installation will be retried later. |
|
9250 |
Error |
The Software Metering Server Manager encountered an error while installing the ODBC Manager on the server %1. The installation will be retried later. |
|
9251 |
Error |
The Software Metering Server Manager encountered an error while installing required ODBC drivers on the server %1. The installation will be retried later. |
|
9252 |
Error |
The Software Metering Server Manager encountered an error while creating an ODBC Data Source Name (DSN) on the server %1. The installation will be retried later. |
|
9253 |
Warning |
The Software Metering Server Manager has installed a newer version of ODBC on the server %1. Reboot %1 in order to complete the upgrade process. |
|
9254 |
Error |
The Software Metering Server Manager encountered an error while copying files to %2 on the server %1. The installation will be retried later. |
|
9255 |
Error |
The Software Metering Server Manager encountered an error while trying to install the ODBC installation service on the server %1. The installation will be retried later. |
|
9256 |
Error |
The Software Metering Server Manager encountered an error while trying to configure the software metering server installation on the server %1. The installation will be retried later. |
|
9257 |
Error |
The Software Metering Server Manager could not configure the database on the software metering server %1. Solution: Stop sharing %2 and then delete the directory that was shared as LicMtr. The service will retry the installation later. |
|
9258 |
Error |
The Software Metering Server Manager could not update the service settings on the software metering server %1. Solution: Stop sharing %2 and then delete the directory that was shared as LicMtr. The service will retry the installation later. |
|
9259 |
Error |
The Software Metering Server Manager could not create the “sender” between the software metering server %1 (on the %2 share) and the site %3. |
|
9260 |
Error |
The Software Metering Server Manager encountered an error while trying to install or start the software metering server service on %1. Possible cause: Security violation. Solution: Make sure that the Service account’s password on %1 is the same as the one assigned to the software metering server. Stop sharing %2 and then delete the directory that was shared as LicMtr. The service will retry the installation later. |
|
9261 |
Error |
The Software Metering Server Manager could not insert the software metering server %1 into the ABCSRVCG table on the site server. Solution: Stop sharing \\%1\LicMtr and then delete the directory that was shared as LicMtr. The service will retry the installation later. |
|
9262 |
Error |
The Software Metering Server Manager could not synchronize the data from the site server %2 to the software metering server %1. |
|
9263 |
Error |
The Software Metering Server Manager encountered an unknown error while updating the site control file. |
|
9264 |
Informational |
The Software Metering Server Manager will remain idle for %1 minutes. |
|
9265 |
Error |
The Software Metering Server Manager could not update the service password on %1. Possible cause: Insufficient permissions. Solution: Make sure that the Software Metering Server Manager’s account has sufficient permissions to perform this operation. |
|
9266 |
Error |
The Software Metering Server Manager could not determine the operating system of the software metering server %1. |
|
9267 |
Warning |
The removal of the software metering server %1 from the software metering client’s list of available servers has not yet been accepted by the site configuration manager. The Software Metering Server Manager will wait for %2 seconds until retrying. |
|
9268 |
Error |
The Software Metering Server Manager could not remove the software metering server %1 from the software metering client’s list of available servers. |
|
9269 |
Error |
The Software Metering Server Manager encountered an error while obtaining the software metering client’s list of available servers from the site control file. |
|
9270 |
Error |
The Software Metering Server Manager could not remove the software metering server %1 from the software metering database when attempting to deinstall the server. |
|
9271 |
Warning |
The Software Metering Server Manager does not return licenses, and checked out licenses, to the site server during the deinstallation of a software metering server. |
|
9272 |
Error |
The Software Metering Server Manager could not stop the service on the software metering server %1. |
|
9273 |
Error |
The Software Metering Server Manager could not deinstall the service on the software metering server %1. |
|
9274 |
Error |
The Software Metering Server Manager could not remove the files on the share %1. You might want to remove these files yourself. |
|
9275 |
Error |
The Software Metering Server Manager could not remove the share %1. |
|
9276 |
Error |
The server called %1 is shut down, not a Windows NT server, or the Service account has been denied access. |
|
9277 |
Informational |
The version of the Software Metering Server service on %1 is %2.%3. |
|
9278 |
Informational |
The server %1 is running %2. |
|
9279 |
Error |
The Software Metering Server Manager could not find the software metering server files for %1 on the UNC path %2. Solution: Make sure that the software metering server is running and installed correctly. |
|
9280 |
Error |
The Software Metering Server Manager could not initialize the software metering server %1. Solution: If you have removed the software metering server installation on %1, also remove the server from the Software Metering Server page and add the server again. If you have not removed the software metering server installation, make sure that the Site Server Service account has administrative privileges on %1. |
|
9281 |
Informational |
The Software Metering Server Manager successfully initialized the software metering server %1. |
|
9282 |
Error |
The Software Metering Server Manager could not deinitialize the software metering server %1. |
|
9283 |
Informational |
The Software Metering Server Manager successfully deinitialized the software metering server %1. |
|
9284 |
Error |
The Site Server Scheduler service encountered a problem (%1). |
|
9285 |
Error |
The Site Server Scheduler service encountered a database problem while updating the schedules (%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9286 |
Error |
The Site Server Scheduler service encountered an unknown problem while updating the schedules. |
|
9287 |
Error |
The service encountered a database problem while packing the database (%1). |
|
9288 |
Error |
The service encountered an unknown error while packing the database. |
|
9289 |
Error |
A database error was encountered while the application was checking the collation inbox (%1). |
|
9290 |
Error |
An unknown error was encountered while the application was checking the collation inbox. |
|
9291 |
Error |
A database error was encountered while the application was checking the license receipt inbox (%1). |
|
9292 |
Error |
An unknown error was encountered while the application was checking the license receipt inbox. |
|
9293 |
Error |
A database error was encountered while the application was checking the license inbox (%1). |
|
9294 |
Error |
An unknown error was encountered while the application was checking the license inbox. |
|
9295 |
Error |
A database error was encountered while the application was checking the table inbox (%1). |
|
9296 |
Error |
An unknown error was encountered while the application was checking the table inbox. |
|
9297 |
Error |
A database error was encountered while the application was checking the collation receipt inbox (%1). |
|
9298 |
Error |
An unknown error was encountered while the application was checking the collation receipt inbox. |
|
9299 |
Error |
A database error was encountered while the application was checking the license receipt inbox (%1). |
|
9300 |
Error |
An unknown error was encountered while the application was checking the license receipt inbox. |
|
9301 |
Error |
A database error was encountered while the application was checking the alert inbox (%1). |
|
9302 |
Error |
An unknown error was encountered while the application was checking the alert inbox. |
|
9303 |
Warning |
A collation receipt (%1) was received at this site when no files were sent. |
|
9304 |
Error |
A database error was encountered while the application was checking the current status of a current collation receipt (%1). |
|
9305 |
Error |
An unknown error was encountered while the application was checking collation receipt current status. |
|
9306 |
Error |
A database error was encountered while the application was expiring collation receipts (%1). |
|
9307 |
Error |
An unknown error was encountered while the application was expiring collation receipts (%1). |
|
9308 |
Warning |
A license receipt (%1) was received at this site when no files were sent. |
|
9309 |
Error |
A database error was encountered while the application was checking the current status of license receipts (%1). |
|
9310 |
Error |
An unknown error was encountered while the application was checking the current status of license receipts. |
|
9311 |
Error |
A database error was encountered while the application was expiring license receipts (%1). |
|
9312 |
Error |
An unknown error was encountered while the application was expiring license receipts (%1). |
|
9313 |
Error |
A database error was encountered while the application was reintegrating %1 licenses for (%2 (%3,%4,%5)) receipts (%6). |
|
9314 |
Error |
An unknown error was encountered while the application was reintegrating %1 licenses for (%2 (%3,%4,%5)) receipts. |
|
9315 |
Error |
An error was encountered while the application was sending licenses to the parent site. |
|
9316 |
Error |
An error was encountered while the application was integrating a license parcel. |
|
9317 |
Error |
A license parcel was received from a remote site but could not be reintegrated. |
|
9318 |
Error |
A database error was encountered while the application was creating the license parcel (%1). |
|
9319 |
Error |
An unknown error was encountered while the application was creating the license parcel. |
|
9320 |
Error |
A database error was encountered while the application was creating the request parcel (%1). |
|
9321 |
Error |
An unknown error was encountered while the application was creating the request parcel. |
|
9322 |
Error |
A database error was encountered while the application was integrating a parcel (%1). |
|
9323 |
Error |
An unknown error was encountered while the application was integrating a parcel. |
|
9324 |
Error |
A database error was encountered while the application was validating parcel licenses (%1). |
|
9325 |
Error |
An unknown error was encountered while the application was validating parcel licenses. |
|
9326 |
Error |
A database error was encountered while the application was adding licenses to the server (%1). |
|
9327 |
Error |
An unknown error was encountered while the application was adding licenses to the server. |
|
9328 |
Error |
A database error was encountered while the application was enumerating requested products (%1). |
|
9329 |
Error |
An unknown error was encountered while the application was enumerating requested products. |
|
9330 |
Error |
A database error was encountered while the application was enumerating products (%1). |
|
9331 |
Error |
An unknown error was encountered while the application was enumerating products. |
|
9332 |
Error |
A database error was encountered while the application was finding products (%1 (%2,%3,%4 (ref:%5))) balancing information (%6). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9333 |
Error |
An unknown error was encountered while the application was finding products (%1 (%2,%3,%4 (ref:%5))) balancing information. |
|
9334 |
Error |
A database error was encountered while the application was adding product (%1 (%2,%3,%4) quantity: %5) receipt information(%6). |
|
9335 |
Error |
An unknown error was encountered while the application was adding product (%1 (%2,%3,%4) quantity: %5) receipt information. |
|
9336 |
Error |
A database error was encountered while the application was removing product (%1 (%2,%3,%4) quantity: %5) licenses(%6). |
|
9337 |
Error |
An unknown error was encountered while the application was removing product (%1 (%2,%3,%4) quantity: %5) licenses. |
|
9338 |
Error |
A database error was encountered while the application was checking if a product was in the software metering database (%1). Possible cause: SQL Server problem. Solution: Verify the following: 1. This computer can reach the SQL Server computer. 2. SQL Server services are running. 3. SMS can access the SMS site database. 4. The SMS site database, transaction log, and tempdb are not full. 5. There are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. After you verify the above, or if the problem persists, check the SQL Server error logs. |
|
9339 |
Error |
An unknown error was encountered while the application was checking whether or not a product was in the software metering database. |
|
9340 |
Error |
A database error was encountered while the application was calculating license store for product %1 (%2,%3,%4) (%5). |
|
9341 |
Error |
An unknown error was encountered while the application was calculating the license store for product %1(%2,%3,%4). |
|
9342 |
Error |
A database error was encountered while the application was adding %5 licenses for product (%1 (%2,%3,%4) (%6). |
|
9343 |
Error |
An unknown error was encountered while the application was adding %5 licenses for product (%1 (%2,%3,%4)). |
|
9344 |
Error |
A database error was encountered while the application was getting a product reference for %1 (%2,%3,%4) (%5). |
|
9345 |
Error |
An unknown error was encountered while the application was getting a product reference for %1 (%2,%3,%4). |
|
9346 |
Error |
A database error was encountered while the application was getting a receipt reference (%1). |
|
9347 |
Error |
An unknown error was encountered while the application was getting a receipt reference. |
|
9348 |
Error |
Balancing information could not be found for product %1 (%2,%3,%4) (ref: %5). |
|
9349 |
Warning |
The license count for a product was truncated to 2,147,483,647. %5 licenses were lost for product %1 (%2,%3,%4). |
|
9350 |
Error |
The CRC check for offline data file %1 failed. |
|
9351 |
Warning |
This site’s parent has attempted to replicate an excluded program (%1) that is currently registered to this site; therefore, the program was not added to this site’s list of excluded programs. |
|
9352 |
Warning |
The product %1 has been replicated from the parent site. Because this program also appeared in the list of excluded programs at this site, it has been removed from this list. |
|
9353 |
Informational |
A new software metering client was detected by the software metering server %1 (computer %2, user %3) at %4. |
|
9354 |
Informational |
The parent site has taken ownership of the product (%1) because it has an identical product registered. |
|
9355 |
Error |
There is a product (%1) registered at this site that conflicts with a product (%2) registered at this site’s parent. Possible cause: The parent site could not take ownership of the product because either the language or time zone property at one of the sites is set to ANY. Solution: To resolve this conflict, remove the product from this site so that the parent site can replicate the product. |
|
9356 |
Warning |
There is a program aliased (%1) at this site that is a registered product (%2) at the parent site. The alias has been removed from this site so that the product could be registered by the parent site. |
|
9357 |
Informational |
The parent site has taken ownership of an excluded program (%1) that appears in the list of excluded programs at both this site and at the parent site. |
|
9358 |
Warning |
The parent site could not add the alias (%1) because this program is a product (%2) at this site. |
|
9359 |
Warning |
The product (%1) at the parent site has a different list of aliased programs than the product at this site. The list of aliased programs at this site has been updated to include only the programs listed at the parent site. |
|
9360 |
Error |
Intersite license balancing attempted to send %1 licenses of %2 (version %3, language %4, time zone %5) to another site. Possible cause: No receipt was received from the destination site, so these licenses have been reclaimed by this site. This might have left the software metering system with an excess number of licenses. Solution: Check the number of licenses in the system and make any necessary adjustments. |
|
9361 |
Error |
No receipt has been received for some collated data that has been sent to the parent site server. This could cause duplicate data to appear at the parent site server because this site will resend the affected data. |
|
9362 |
Error |
An error was encountered while the application was deleting removed aliases (DSN=%1). |
|
9363 |
Error |
The application could not connect to software metering server (%1). |
|
9364 |
Error |
The peak use for product reference number %1 over %2 days could not be calculated (%3). |
|
9365 |
Error |
The peak use for product ref %1 for the period %2 days could not be calculated (%3). |
|
9366 |
Error |
The ABCPEAK table could not be accessed to calculate the trend from %1 over %2 days (%3). |
|
9367 |
Error |
The ABCPEAK table could not be written to at %1 for the product %2 (%3). |
|
9368 |
Error |
The application could not write zero values to ABCPEAK table (%1). |
|
9369 |
Error |
Could not enumerate the software metering servers at this site (%1). |
|
9370 |
Error |
Unknown software metering server (%1). |
|
9371 |
Error |
Deinitialization error (%1). |
|
9372 |
Error |
The field %1 in the CALCTBAL table could not be read for the product %2 (%3). |
|
9373 |
Error |
Could not read the CALCTBAL or PRODUCT tables (%1). |
|
9374 |
Error |
There was an error writing to the LBPRODIS or LBPRODL table (%1). |
|
9375 |
Warning |
ODBC tracing is turned on at the server %1. This might be affecting the performance of the server. |
|
9376 |
Error |
The Software Metering Server Manager could not locate %1 on the network. Solution: Make sure that the account %2 on %3 (which is being used by the Software Metering Server Manager service) has access to the server %1. The account will need administrator privileges on %1 so that shares, accounts, and services can be updated. |
|
9377 |
Error |
The Software Metering Server Manager has been denied access to %1. Solution: Make sure that the account %2 on %3 (which is being used by the Software Metering Server Manager service) has access to the server %1. The account will need administrator privileges on %1 so that shares, accounts, and services can be updated. |
|
9378 |
Error |
An internal system error was encountered while the application was trying to access %1. |
|
9379 |
Error |
The Software Metering Server Manager does not have sufficient privileges to %1. Make sure the Software Metering Server Manager’s account %2 has administrative privileges on %1. |
|
9380 |
Error |
The local directory for the software metering server files, %1, is in an unrecognizable format. The Software Metering Server Manager is unable to use this directory at the server %2. |
|
9381 |
Error |
There was an error in copying files from the site server to the software metering server %1. |
|
9382 |
Error |
There was an error in copying files from the site server to the software metering server %1 because a required file could not be found. |
|
9383 |
Error |
There was an error in copying files from the site server to the software metering server %1 because of a bad path. |
|
9384 |
Error |
There was an error in copying files from the site server to the software metering server %1 because the site server has too many open files. |
|
9385 |
Error |
There was an error in copying files from the site server to the software metering server %1 because the software metering server’s directory is full. |
|
9386 |
Error |
There was an error in copying files from the site server to the software metering server %1 because of a hardware I/O error. |
|
9387 |
Error |
There was an error in copying files from the site server to the software metering server %1 because the software metering server’s disk is full. |
|
9388 |
Error |
There was an error in copying files from the site server to the software metering server %1 because the Software Metering Server Manager was denied access to %1. |
|
9389 |
Error |
There was an unidentified error in copying files from the site server to the software metering server %1. |
|
9390 |
Error |
There was an error in copying files from the site server to the software metering server %1 because of a sharing violation. |
|
9391 |
Error |
There was an error in copying files from the site server to the software metering server %1 because of a lock violation. |
|
9392 |
Error |
The Software Metering Server Manager could not create the Software Metering Server Service account %1 locally at the server %2. If you create the %1 service account at %2, the Software Metering Server Manager will use it when the installation is retried. |
|
9393 |
Error |
The Software Metering Server Manager could not assign the ‘Logon as a service’ right to the Software Metering Server Service account %1 at the server %2. This will prevent the Software Metering Server service from starting. If you grant the Service account %1 this privilege, the Software Metering Server Service will use it when the installation is retried. |
|
9394 |
Error |
The Software Metering Server Manager could not assign the Software Metering Server Service account %1 administrative privileges at the server %2. This privilege is required for the installation and management of ODBC on %2. |
|
9395 |
Error |
The Software Metering Server Manager has been denied access to install the service %1. Make sure that the Software Metering Server Manager’s account %2 has sufficient privileges to install services on %3. |
|
9396 |
Error |
The service %1 does not recognize the account %2 on %3 and will not install. If you create the account %2 at the server %3, the service will be installed when the operation is retried. |
|
9397 |
Error |
The server %1 is reporting that the service %2 has an invalid name. The service cannot be installed. |
|
9398 |
Error |
The server %1 already has a service called %2. The service cannot be installed. |
|
9399 |
Error |
The Software Metering Server Manager failed to install the service %1 on %2. |
|
9400 |
Error |
The Software Metering Server Manager failed to start the service %1 on %2.%3 |
|
9401 |
Error |
The Software Metering Server Manager cannot find the Service account %1 on %2. |
|
9402 |
Error |
The Software Metering Server Manager has created the Service account %1 on %2. |
|
9403 |
Error |
The Software Metering Server Manager could not change the Service account on %1 for the service %2. |
|
9404 |
Error |
The Software Metering Server Manager could not install the ODBC installation service on %1. |
|
9405 |
Error |
The Software Metering Server Manager could not start the ODBC installation service on %1. |
|
9406 |
Error |
The Software Metering Server service is not running on %1. |
|
9407 |
Error |
The site server was unable to connect to the software metering server %1 during license balancing. Make sure that %1 is accessible to the site server services. |
|
9408 |
Error |
There was an error reading the scheduling information from the database. The error returned was %1. |
|
9409 |
Error |
There was an error getting the information about this site’s parent from the database. The error returned was %1. |
|
9410 |
Error |
There was an error removing the information about this site’s parent from the database. The error returned was %1. |
|
9411 |
Error |
This site’s parent has not yet created a software metering outbox. |
|
9412 |
Error |
There was an error while copying files. The error returned was %1. |
|
9413 |
Error |
There was an error while reading the database when the application was trying to establish the type of link to the parent site %1. The error returned was %2. |
|
9414 |
Error |
There was an error while writing schedule information to the database for the site %1. The error returned was %2. |
|
9415 |
Error |
There was an error removing the local replication event. The error returned was %1. |
|
9416 |
Warning |
ODBC tracing is currently enabled on the software metering server %1. This can have a serious effect on the performance of the software metering server. |
|
9417 |
Error |
There was an error while the application was accessing the database. |