Palisade Knowledge Base

Knowledge Books

• Knowledge Books
• Standalone Licenses
• Network Guide
• More on Networks
• End User Setup
• Techniques and Tips
• Troubleshooting
• Licencias individuales
• Guía para Administradores de Red
• Licencias de red
• Configuración de usuario final
• Técnicas y Consejos
• Soluciones
• Licenças Standalone
• Licenças de Rede
• Configuração do usuário final
• Técnicas e Dicas
• Soluções
• Obsolete Articles

• Main Support Page

Home → Troubleshooting → All Products: Startup → "Timeout creating the named pipe"

2.87. "Timeout creating the named pipe"

Applies to:
Palisade software, releases 6.x/7.x/8.x

When I try to launch my software, I get this error message:

Authorization failure
Details: Timeout creating the named pipe \\.\pipe\RPC pipe for PalFlexServer(X).exe, processId=0

There are a number of possible causes and cures. Here are the ones we're aware of from customer experiences:

• Have you tried restarting Windows? Sometimes Windows gets itself into a bad state, and when you restart Windows it repairs itself. This is not just a matter of logging off and on, but restarting Windows (rebooting).

• Is the FLEXnet Licensing Service enabled? Click Start » Run, enter the command services.msc and press the Enter key. Scroll down to FLEXnet Licensing Service. Look at Startup Type, which should be Manual. Look also at Status:

  • If Status is Started, the service is installed correctly and running normally.
  • If Status is blank, right-click the service and select Start. If Status changes to Started, the service is installed correctly. If Status does not change, press F5 to refresh the window. If the service cannot start, that's the problem. First try repairing the Palisade software. If that does not solve the issue, either contact Technical Support or try uninstalling and reinstalling the software, making sure to run the installer as administrator.

• Does your installation allow only specified programs to run? Have your administrator specify PalFlexServer6.exe as an allowed program.

• Do you have Excel 2007? Make sure that your Service Packs are up to date, and then run a repair.

• Is your hardware going bad? We have had reports of this error shortly before a hard drive failed. Run the manufacturer's hard-drive checker, and run a good third-party RAM tester.

Last edited: 2020-04-16