SIMS.Net - problem importing new reports [SOLVED]

[bossman]

I used to use below script for early Sims system before the .Net framework version.

 

@echo off

SET LANID=2J

\\

cd \\PC-SERVER\F$\CAPITA\SIMS

SIMSMAN.EXE %1 %2"

 

as sims did not recognise the workstation you had to create a workstation in old dos mode using win95 clients then you had to set the lanid for that particular workstation. You then had to set up a user account for that workstation and set all permissions through this account. Bit long winded but there you go. This should not be affecting your clients but as you say I would rename to old. Hope this helps you further.

[Guest]

Ahhhh the joys of LAN IDs. How I miss SIMS..... NOT

[DMcCoy]

Is the document manager server running properly? Tools -> Setups -> Document manger server. Click the "test server connection" button, you should get a "server ok" response. Have you also tried the database diagnostics? (backup first! ). I suspect it could just be the doucment manager though.

[Irazmus]

@bossman: OK, so it seems my assumption was a little off. I didn't have the 'pleasure' of pre .Net SIMS. Renamed to .old, no difference.

 

@DMcCoy: The Document Manager is running, the connection test returns 'OK' when used with the hostname, but fails when using the IP (one of the biggest mysteries thus far)

Havn't tried the DB diagnostics, and I'll hold off on that until I speak with the LSU again.

 

We can add to the list of attempted fixes:

* Uninstall and reinstall the Document Server

[glensc]

@bossman: OK, so it seems my assumption was a little off. I didn't have the 'pleasure' of pre .Net SIMS. Renamed to .old, no difference.

 

@DMcCoy: The Document Manager is running, the connection test returns 'OK' when used with the hostname, but fails when using the IP (one of the biggest mysteries thus far)

Havn't tried the DB diagnostics, and I'll hold off on that until I speak with the LSU again.

 

 

Possibility...

Is document manager using a webserver interface on the server. In which case the conection is probably using HTTP1.1 host headers, ie using the header info to conect to the corect virtual website, using the IP it's not getting that info and failing.

[Irazmus]

@glensc: That's a very interesting point. The document server is certainly using HTTP1.1.

 

Running SmartSniff while doing a (successful) connection test gives the following.

 

On the client:

HTTP/1.1 100 Continue

HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Server: MS .NET Remoting, MS .NET CLR 1.1.4322.2300
Content-Length: 611




true

 

On the server:

POST /DocumentServer.rem HTTP/1.1
User-Agent: Mozilla/4.0+(compatible; MSIE 6.0; Windows 6.0.5384.0; MS .NET Remoting; MS .NET CLR 1.1.4322.2032 )
Content-Type: text/xml; charset="utf-8"
SOAPAction: "http://schemas.microsoft.com/clr/nsassem/SIMS.DocumentServer.IDocumentServer/DocumentServerInterfaces#Ping"
Content-Length: 572
Expect: 100-continue
Host: odin:8080

 

That might explain that oddity

[Irazmus]

After many long weeks of searching we finally have a solution.

The problem was caused by a ghost entry for the old Document Server hiding in the system which only became visible after removing the current document server from the 'Document Server Setup' dialog, and therefore hadn't been noticed previously. Once this ghost record was removed and the current server added back, we were once again able to import reports, and my SIMS manager is happy again.

 

Thanks again for all your help and suggestions.