Winsocket application failed to link on Windows XP with VS 6

Posted on by
Reply

I wanted to make a server application in C++ with Visual Studio 6. Although I included winsock2.h, ws2tcpip.h and ws2_32.lib in my cpp:

#include <winsock2.h>
#include <ws2tcpip.h>
#pragma comment(lib,"Ws2_32.lib")

I still was unable to build the project and got the errors:

Server.obj : error LNK2001: unresolved external symbol _freeaddrinfo@4
Server.obj : error LNK2001: unresolved external symbol _getaddrinfo@16

The getaddrinfo and freeaddrinfo functions were added to the Ws2_32.dll on Windows XP and later. Looking with the Dependency Walker indeed the functions were there. I thought then that the ws2_32.lib that came with Visual Studio 6.0 installation was too old. I hoped that the installation of the latest service pack for Visual Studio 6 can fix the problem, but it did not.

The solution was to get a newer version of the library and the ws2tcpip.h from a newer Visual Studio installation.

On the client side

Posted on by
Reply

Much of the effort is concentrated on the server side of tuning, be it the Oracle Database, PDM solution, visualization, replication servers. But what happens on the client side in which CAD tools are under heavy use in connection with the PDM systems like Windchill PDMLink?

A check list can be summarized:
1. LAN/WAN latencies: ping and other network tools.
2. Use PTC’s Windchill Single User Performance Tester, you can automate performance tests that time the interaction between Pro/ENGINEER Wildfire and a Windchill server.
3. Windchill Client Inspector available since Windchill 10.0. Useful to gather system information and apply certain system and browser tweaks.
5. ProE/Creo parameters in config.pro
6. Related tables and workspaces settings in My Settings -> Preferences.
7. Defragmentation on the system and inside the VM.

PTC’s System Monitor for Windchill 10.1

Posted on by
Reply

A new release version 10.1 of Windchill is around the corner. One handy tool for System Administrators is also released as a separate module with a lot more features: PTC System Monitor. The application is useful to detect, diagnose and repair problems within the PLM environment. It is also compatible with prior versions of Windchill 9.1 and 10.0.
Features: check system and components health, specify thresholds and notifications, capture transaction informations across application tiers and software components eg. check-in/out.

Until now I have used the Monitoring Tools from the Server Status page to monitor and set levels of information I wanted to see in the logs. Looking forward to test the new PSM.