K3 application troubleshooting
First quarter installation and upgrade
1. Fault Phenomenon: After the customer is logged in as a working group user, the K3 system can't find the intermediate layer server, that is, it is not convinced.
Worker. If the workgroup user uses administrator and the password and the server can be positive
I am constrained.
Workaround: The server-side security mechanism limits the user's access to the server. Just need to serve
Add corresponding usernames and passwords in user management of the server.
For example: ABC users have been added to the server user, and the password 123 is in the workgroup user identity.
When logging in, if the user ABC, the password 123 can use K3 normally.
2. Fault Phenomenon: When the k3 intermediate layer is installed, the installation error Error, MSVCRT40. DLL can't be covered
Cover, etc.
Workaround: In Windows2000, the prompt cannot be covered, it is not necessary to pay attention to it.
Windows98, ME, close all background runners, reinstall the intermediate layer.
3. Fault Phenomenon: When the client registers the intermediate layer, it is found that the intermediate server cannot be found.
Workaround: 1. First check if the network is smooth, use the ping tool to check, in Windows
In the DOS mode, enter the following command: ping 10.10.1.1 (server IP is 10.10.1.1)
2. If the above appears, the network is unblocked, then check the network configuration.
4. Fault Phenomenon: Single-machine installation, no NIC, K3 installation prompts that the intermediate layer cannot be connected.
Workaround: WINDOWS2000, join the network card - Microsoft Loopback Adapter
Dial-up adapter is added to Windows98, ME.
At the same time, it must be added to the TCP / IP protocol.
5. Fault Phenomenon: The client's client is distributed in three regions (a headquarters, two divided millions), and established through the Telecommunications Bureau
VPN, the division factory is installed after the K3 client is not connected to the headquarters.
Workaround: Track by tracert command, Isors the division of labor through two gateways (internal 192.168.1.1
And 192.1.1.250) is connected to the headquarters. In the client's TCP / IP protocol, gateway items are added
192.168.1.1 and 192.1.1.250 Two IPs can be normal.
6. Fault Phenomenon: This software must be safe in the system administrator group in the Windows NT environment.
?
Solution: Replace the operator, log in to the system administrator or as level
The client allows the operator to install and operate as a standard user (PowerUser).
7. Fault Phenomenon: This application requires [Intermediate Layer] and [Client] environment to install TCP / IP protocol, stand
Install the protocol?
Workaround: Install the TCP / IP protocol, it is best to use a static IP address. Dynamic IP addresses are also available, but the efficiency is lower.
8. Fault Phenomenon: The MTS2.0 is installed correctly, please first install NTOPTIONPACK.
Workaround: This problem is only available on Windows, installs NtOptionPack on the K3 installation disc.
NT SP4 above the patch.
9. Fault Phenomenon: Basic system file installation failed, please check the contents of the log file [ERRORS].
Workaround: Press CRTL Alt Del to stop the procedures that are running in the system in the system, and then reinstall.
10. Fault Phenomenon: Basic system file registration failed, please check the contents of the log file [REGERRORS].
Workaround: Press CRTL ALT DEL, stop the procedure that is running in the system in the system, then
re-install.
11. Fault Phenomenon: DCOM system file is lost.
Workaround: Reinstall DCOM95 (Windows95), DCOM98 (Windows98) or
DCOM98EX (second edition of Windows98),
Installer location K3 mounting disk / OS / ...
12. Fault Phenomenon: Need object.
Workaround: Installation disk program file error, version does not correspond or problems during installation, need to be reinstalled
K3 system client to ensure that corresponds to the intermediate layer version.
13. Fault phenomenon: Windows9x must be installed DCOM98
Workaround: Install DCOM98, installer location K3 installation disk / OS / ...
14. Fault Phenomenon: This system does not support Chinese machine names, please modify the machine named "
name.
Workaround: Server: You can only use standard English name
Client: Change the machine name to a standard English name before installation, change the original name after installation.
15. Fault phenomenon: the intermediate layer connection failed
Solution: 1. Confirm that the client and the intermediate layer use the same version, and there is access to the server where the intermediate layer is located.
Authority
2. Reinstall the client, intermediate layer.
16. Fault Phenomenon: Intermediate Layer Server does not act as a remote server (may be Windows 9x)
Workaround: Install the intermediate layer on Windows2000 or WindowsNTServer
17. Fault Phenomenon: The system OLE may not be normal when logging in to the system.
Workaround: Reinstall the K3 intermediate layer
18. Fault Phenomenon: Cross-domain client cannot access the intermediate layer
Solution: Establish the same user, password, or two domains simultaneously in both domains.
19. Fault phenomenon: After the K3 is installed, when the client click the business handling document, the prompt is prompted.
BillDataAccess is not registered correctly, ativex error.
Solution: 1. Re-register or install the intermediate layer server;
2. Replace the BillDataAccess intermediate layer assembly, steps below:
1, possible words, stop IIS service, as shown
2, open the MTS manager as shown
3, delete components as shown
4, replacement components are shown
20. Fault Phenomenon: This Software Must Running Under PWindows Or Ewindows Richwin!
Workaround: This prompts are not to run Richwin for English Windows operating systems. Installation or run
Richwin.
21, Fault Phenomenon: System Config Error!
Workaround: This prompt is because the operating system has no system language. Check if the operating system has at least one default
The language, if not installed or set, if it is an operating system installed on the pirated disc,
It can be due to the lack of these files on the pirated disc itself, can replace an operating system disc reload operation
system.
22. Fault phenomenon: This system must run in Windows 4.0 and above!
Solution: This prompt is because NT Server or NT Workstation version is less than 4.0. Replace the operating system greater than or equal to 4.0.
23, the fault phenomenon: can't load setup.oss!
Workaround: This prompt is because the disc is damaged or damaged on the disc. Replace the installation disc.
24. Fault phenomenon: can't Find Isadmin Point!
Workaround: Because the program entry cannot be found when installing the intermediate layer, the reason may be because some applications open, production
Have a shared conflict. Close the programs other than the installer in the task manager, and then install.
If you can't, you can check if there are other conflicts, and it is best to reload the operating system.
25. Fault phenomenon: This system requires MSDTC system service support, please install the service!
Workaround: This prompt is because SQLServer's MSDTC service is not installed or does not start this service.
. If you have installed it to start MSDTC in SQLServer Service Manager, no
The installation is installed.
Figure 1 Check MSDTC service
26, the fault phenomenon: please check if SQL Server 7.0 is installed correctly, whether the SQL Server 7.0 service is started!
Solution: This tip may be destroyed by SQL Server 7.0, but the maximum may still start SQL
Server7.0 service. Start SQL Server
Figure 2 Check MSSQLSERVER service
27. Fault phenomenon: You cannot get your domain user information, please log in with a named user!
Workaround: If you do not set it to a domain user in user management, use the domain user mode
The record will prompt this information, so the user can only log in with a named user. Please use a name
Users log in.
Second, backup and recovery (example operation of sp_attach_db, sp_detach_db)
28. Fault phenomenon: SQL Server is destroyed, the entity of the database is still in, and the data entity needs to be restored after reloading.
Solution:
For example: data entity AIS20010501121212_DATA.MDF and AIS20010501121212_log.ldf
The path of the entity C: / Data
Connection: Run in Query AnalySer:
EXEC SP_ATTACH_DB @ dbname = N'AIS20010501121212 ',
@ Filename1 = N'c: /DATA/AIS20010501121212_DATA.MDF '
@ Filename2 = N'c: /DATA/AIS20010501121212_Log.ldf '
Section 3 Data Repair and Processing (Check, Checkdb (), Reindexdb, etc.)
SQL Server database may damage due to some of the following reasons:
1. Operation problems, including cold starters, hot disk, delete some database files;
2, hardware issues, including disk controllers;
3. Operating system issues, including some fatal errors related to the system.
We can take some precautions:
1. Perform ChkDSK (without parameters) during regular / regularity to detect the physical structure of the hard disk and fix some
Chkdsk report;
2, often backup data.
Although there are more precautions, the damage is difficult to avoid, and when the database is damaged, we can take some solutions:
29, fault phenomenon: Domestic database is damaged, how to test. Solution:
The correctness of the allocation and structure of each object in the database can be detected by DBCC CHECKDB, and all error messages can be displayed by a parameter control. The syntax is as follows:
DBCC CHECKDB
('Database_name' [, NoIndex | {REPAIR_ALLOW_DATA_LOSS
| Repair_fast
| Repair_Rebuild
}]
[With {all_errormsgs | no_infomsgs}]
Parameter Description:
'Database_name' represents the detected database entity name;
NoIndex refers to non-collective indexes of the system table.
REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD refers to a direct repair of the discovered error, where the REPAIR_ALLOW_DATA_LOSS is represented, if this error cannot be fixed, the system will directly delete the relevant data directly. When either of these three parameters, the database must be in a single user mode and set in the database properties in Enterprise Manager;
All_errormsgs represents all of the detected error messages, otherwise, only 200 error messages are displayed for each table;
NO_INFOMSGS represents a report that hides all information and occupies space.
After testing, for the wrong object, the specific error information will be reported in the form of the Object ID, and the relevant table can be found in the Object ID to system table sysObjects, namely Name.
30. Fault phenomenon: After the checkdb is detected, there is a problem with the physical storage of the object.
Workaround: You can use DBCC Checkalloc or DBCC CHECKDB:
DBCC Checkalloc ('Database_name' | Repair_rebuild}] [with
{All_errormsgs | no_infomsgs}]
DBCC Checkdb ('DB_NAME', Repair_Rebuild)
31. Fault Phenomenon: After the checkdb is detected, it is found that the index of the non-system object is wrong.
Workaround: You can fix it with DBCC DBREINDEX or DBCC CHECKDB:
DBCC DBREINDEX ([Database.Owner.table_name "[, INDEX_NAME"
FillFactor]]]] [with no_infomsgs]
DBCC CHECKDB ('db_name', repair_rebuild).
32. Fault Phenomenon: When the checkdb is detected, the prompt cannot be established.
Solution: At this time, the database is corrupted. For this situation, we can take the following measures
To try to fix.
First, create a new database in SQL Enterprise (if the database name is TEST), after building the database, stop SQL Server Service Manager, and rename the MDF file of the customer database to test _Data.mdf (the main file name of the new database) , Then overwrite the new database with the name of the name with the name of the new database, then start SQL Server Service Manager. Setting the system table to change status for the Master database
Use master
Go
sp_configure 'allow updates', 1Reconfigure with override
Go
Setting the database as an emergency:
Update sysdatabases set status = 32768 where name = 'database'
Stop and restart SQL Server Service Manager and rebuild the log file:
DBCC TRACEON (3604)
DBCC Rebuild_log ('Test', 'Test _log_ldf')
Set the database to a single user mode, then test:
sp_dboption 'Test', 'Single User', 'True'
DBCC CHECKDB ('Test')
Go
This database performs the checkdb process to find that some tables are destroyed, so the operation of reconstructing the index for the specific table:
DBCC DBREINDEX (Table Name)
If the above operation is not resolved, if the table of index damage is a temporary table or is not a key table, it can be introduced from the new setup. If the primary table, it may be recovered by a recent backup (part). If there is no backup, it cannot be repaired.
33. Fault phenomenon: Database index is destroyed
Solution:
a. Open the Enterprise Management in SQL Server, place this database as "single user mode" in the properties of this database;
b. Execute the following command in Query Analyzer for database repair: DBCC Repair ("dbname", repair_rebuild);
c. After repairing, execute database detection in Query Analyzer: DBCC Checkdb ('DBNAME');
D. If there is no problem after the test is detected, the repair is successful; if it is still an error in the detection, you need to perform a repair command to clean the illegal data in the database, and then upgrade. This fix command is DBCC Checkdb ('dbname', repair_allow_data_loss).
Section IV
34. Fault Phenomenon: After the server changes the computer name, K3 cannot run.
Workaround: The reason is that the server cannot start normally. Reissue database layer or restore original calculation
Machine name.
35. Fault Phenomenon: Tip has other users conflicts, the current function cannot be executed
Workaround: Enter the K3 Network Management Control Tool to clear other operating user information being resident.
36. Fault Phenomenon: Unable to connect to the database
Workaround: 1. Check if the MSDE or standard SQL7 is running normally
2. Reinstall the K3 intermediate layer
38. Fault phenomenon: Automotion error
Workaround: 1. Re-register the intermediate server.
2. Reinstall the client
38. Fault Phenomenon: Modify the password of the SA, enters the client prompt "Defined Application or Object Error"
Solution: Enter the middle layer to modify the password of the account attribute into the correct password.
39. Fault phenomenon: The intermediate layer server does not enter the interactive state, and the K3 system client will not find the prompt.
Intermediate layer server.
Solution:
In general, the K3 product requires an intermediate layer server to enter an interactive state, but can also provide services to implement the server without logging in, the specific configuration steps are as follows: a. If the server NT Server4.0, run the program / Windows NT 4.0 OPTION PACK / Microsoft Transcation Server / Transcation Server Explorer; If the server is Windows2000 Server, the management tool / component service in the program is running; b. For the console root / microsoft transcation server / computer (Computers) / My Computer (My Computer) / Installed Packages / Under All Names Set the Package Setting Properties (Right-click). Select the [Identifier] page and select this user (this user). Enter the domain username and password to determine; c. Run [Start / Run. . . ], Type DCMCNFG Enter. In the subsequent interface, find [KDSVRMGR.CLSACT], double-click the callout property page, select the [Identifier] page, then select this user (this user), the input domain username and password are determined. 40. Fault phenomenon: Tips There are other user conflicts, the current function cannot be executed.
Workaround: Indicates that there is a mutex being executed, or an abnormality exits in a client. Network
Control module, display people and entry time currently being executed, according to time and
Whether the person is decided in operation, if someone is performing this feature, please execute the mutual exclusion later.
Function, if an abnormality exits, you can operate normally by deleting the current record.
41, the fault phenomenon: the general ledger is not checkout?
Workaround: This system has sets with the total business system in the account set parameters.
Synchronize during the account, the total account will check if each subsystem has been checked, otherwise it is not allowed
General accountment. If each business system is to synchronize with the general ledger, please clarify the business system, then
General bill. If the business system is not synchronized with the general ledger, set the account set parameters of each business system.
At the point, the synchronization button is canceled during the general led.
42. Fault phenomenon: Users cannot switch the intermediate layer!
Solution: This unit has been used as an intermediate server, so it cannot be switched. Please use Windows tasks
The intermediate layer can be switched to the manager, turn off the KDSVRMGR task.
43. Fault phenomenon: The system OLE may not normal when logging in to the system!
Workaround: Restart the machine, if you still log in to the K / 3 system normally,
Only the operating system is reinstalled.
