GeneXus Server Common Issues

This could happen when GeneXus Server is installed on machines with IIS 6.0. In this case, the application pool must be configured with the 'Local System' Identity. The Identity by default is 'Network Service.' See GeneXus Server Requirements for more information.

The following issues may occur when trying to connect to a GeneXus Server:

Could not load file or assembly 'SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (Artech.Common.Proxy)

Program Location:
at Artech.Common.Proxy.GXServerClient.HostedKBs(String serverUrl)
at Artech.Core.UI.Dialogs.CreateKBFromServerDialog.btnConnect_Click(Object sender, EventArgs e)

There was no endpoint listening at http://.../TeamWorkService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. (mscorlib)

This is a generic message that is followed by a more specific one:

The remote name could not be resolved: 'xxxxxxxx' (System)

Cause:The server (the machine where GeneXus Server should be running on) may not be accessible (turned off or not connected to the network, for example), its name may be misspelled, or the DNS cannot solve the name.

Solution: Check the server machine is accessible (turn it on or connect it to the network as examples), check spelling or substitute the name by the IP address.

The remote server returned an error: (404) Not Found. (System)

Cause: There is no GeneXus Server running in the selected machine.

Solution: Install GeneXus Server on the chosen machine.

The remote server returned an unexpected response: (405) Method not allowed. (mscorlib) or error: Could not connect to a GeneXus Server instance at the specified URL: 'http://10.1.1.154/gxserver' because there is a protocol mismatch.

These issues are mostly seen when trying to expand a served Knowledge Base to display its available versions.

NoPermissionsOnDB

Cause: GeneXus Server cannot open the served Knowledge Base because the default ASP.Net user does not have connect, read or write permissions over the SQL Server database containing the Knowledge Base.

Solution: Open SQL Server Management Studio, select the Security node, then open the ASPNET user properties and add the required permissions as shown below.

Note: When using Internet Information Server 6.0 or higher, make sure that the Default Application Pool uses the Local System Identity. Open the IIS Manager, select the Application Pools folder, then DefaultAppPool, open the default Properties and choose the Identity tab as details the following image:

Cause: When downloading or uploading a Knowledge Base using the New --> Knowledge Base from Server or File --> Send Knowledge Base options, make sure the client (GeneXus Client) and server-side (GeneXus Server) allow HTTP connections; otherwise, the process could be blocked during the KB transfer step.

error: GeneXusServer - An Error Occurred While Importing File 'ATTRIBUTE'
error: GeneXusServer - An Error Occurred While Importing The Data
error: GeneXusServer - There was an error creating the Knowledge Base but GXServer could not recover. If you want to send it again remove the broken Knowledge Base 'XXX' from the server or send it with a different alias.
error: GeneXusServer - Error cleaning up:'Only user processes can be killed.'

Cause: The installed bcp.exe is not working, running the bcp.exe application without parameters.

Solution: Reinstall 'Microsoft SQL Server Command Line Utilities' and edit the file web.config from the GeneXus Server installation directory adding the following line in the "appSettings" node:<add key="bcpPath" value="<bcp path>\bcp.exe" />
Where <bcp path> is the path the working bcp.exe.

Note: if Microsoft SQL Server Command Line Utilities x64 is not working, install versionx86 and update the web.config to set the right BCP path.

Check the Event Viewer for further information. It seems there's something wrong with the ASP.NET registration within IIS; try registering the ASP.NET again within IIS.
To uninstall it execute the following:

Depending on the Knowledge Base size, communication to the server, etc.rss; Commit and Update operations could need more than 20 minutes to be executed; which is the default timeout configured for these transactions.

In this situation, an error message like the following is shown in the output window:

error: The request channel timed out while waiting for a reply after 00:18:19.8287661. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

To change the default values, edit web.config file located in the GeneXus Server installation directory and modify the receiveTimeout and sendTimeout parameters and edit genexus.exe.config located in the GeneXus installation directory to change TeamDevTimeOut parameter.

web.config

<binding name="GXCustomHttpBinding" ... >

<binding name="GXBinding" ... >

genexus.exe.config

<add key="TeamDevTimeOut" value="nn:nn:nn" />

An attempt was made to load a program with an incorrect format

You might get this error while loading the default page if you're running IIS7 on a 64 bit OS. To fix it go to IIS Management console, go to the advanced settings of the GeneXusServerAppPool application pool and set the property 'Enable 32-bits Applications' to True

The same error appears in Win2003 Server x64 with the following message:

System.BadImageFormatException: is not a valid Win32 application

To enable 32 bits applications open a command prompt, go to %systemdrive%\InetPub\AdminScripts and run the following command:

System.BadImageFormatException: Could not load file or assembly 'GeneXus.Server' or one of its dependencies. An attempt was made to load a program with an incorrect format.

The requested service, 'http://../genexusserver/HelperService.svc' could not be activated. See the server's diagnostic trace logs for more information.

When you get the above error while trying to connect to a GeneXus Server, type the same URL in the web browser; these are the possible errors:

Could not load file or assembly 'App_Web_sf0lfn0j, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Solution: you need to give the Users group of the server Full Control over the Temporary ASP.Net Files folder. This error appears if the temporary files could not be deleted. You can remove them manually by deleting the GeneXus Server folder under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files.

You need to change the IIS configuration to get the real error message. To do that Open de IIS Management Console and do the following:

Select GeneXus Server virtual directory on the left-hand tree view

Open Error Pages from IIS configuration pane

Click on "Edit Feature Settings."

Set the property "When the server encounters an error, return:" to "Detailed Errors."

Restart IIS by executing iisreset from a command prompt.

At least one security token in the message could not be validated

During a Commit or Update the following error may occur:

========== Update started ==========
Contacting GeneXus Server at 'http://sandbox.genexusserver.com/xev1/'... done!
error: At least one security token in the message could not be validated.
Update Failed

Check the Credentials (User and Password) in the Team Development Security dialog.

Could not connect to a GeneXus Server instance at the specified URL: <gxserver url> because there is a protocol mismatch.

Error: An unhandled exception has occurred. A potentially dangerous Request.Form value was detected from the client (GXState="...Caption":"<...")

Solution: The GeneXus Server application pool must be configured to use the framework 2.0. GeneXus Server runs on the framework 3.5, which stands on the framework 2.0. The framework 4.0 and 4.5 and 2.0 are completely different and are not supported.