ianswalker

Capita have now fixed our servers which had the x86 x64 deployment service installer problem. They spent a long time editing the contents of the Solus3 deployment Service database. Why it gets all this incorrect data inserted into it has yet to be explained

It is now getting more complicated. Having tried a few more servers one has the problem for the first time having successfully upgraded Solus3 from 3.4.64 to 107 it now fails on 118. Another that had the problem on 107 is OK on 118. This apparently randon behaviour is very puzzling

All the affected servers (14 of them) are Windows 2003R2 x64. They are all clean installs (no upgrades from previous versions). Solus 3 was installed at version 3.4.64 The next Solus upgrade was OK but the next Solus upgrade failed at the deployment service stage with the upgrade trying to use the x86 rather than x64 installer. Capita fixed this by grubbing about in the solus deployment database and removing some data. The update then proceeded correctly. The same thing has now happened with 3.4.188 so the problem has not been fixed. Capita have all the logs to know what is going on. I have other servers which are Windows 2003 R2 x64 which do not display this problem. Also others which are windows Server 2003R2 x32 which are OK . The Windows servers which are 2008 (x86 and x64) and 2008R2 are all behaving OK. The problem seems to be what is getting put into the Solus database.

Solus 3.4.118 seems to suffer the same problem as 3.4.107 in that it fails to update the deployment service with a Windows errror. 'this is a 64-bit machine Please use the 64-bit installer'. This is caused by additional entries in the database which tells the installer that a 32-bit version is required. It is getting this wrong. How about a fix for this soon?

Latest update after Capita have had a look at the problem. The cause of the failure to update the Solus to.3.1.107 is extra entries in the Solus3_deployment_database which incorrectly tell the deployment service updater to use the x86 installer rather than the x64 version. Removing these offending entries using SQL 2008 management studio then allows the update to proceed without error. However Capita don't know why these entries get there in the first place. Hopefully we will have an answer to that soon.

The Server architecture is Windows 2003 R2 64-bit. I'll try re-downloading the package. Previous Solus 3 updates have worked OK Ticket logged with Capita but as yet no response

Solus 3 and its bits are installed in c:\Program Files\Solus i.e a 64-bit installation. However the Solus 3 database command folder is in c:\Program Files (x86)\Solus

Hi all When deploying the latest Solus 3 update on some 64bit servers the upgrade fails with an unknown error. Looking at the application part of the event viewer gives the message: 'Product: SOLUS 3 Deployment Service -- This is a 64-bit operating system. Please use the x64 version of this installer. ' I have talked to Capita who say the problem needs to be refered to the developer but this has happened before. Any ideas as to what is going on. Ian

Genius! That fixed it Thanks very much

The Sophos AV does have Firewall but this is turned off too

Nothing special here. All servers are on separate independent sites. I mention the number so to avoid being asked a lot of routine questions. Solus 3.4.64.0 is the version being installed. It is on a Windows 2003 R2 x64 server. The process of installation goes fine. After registering the site and telling Solus which server is hosting the deployment service an agent is usually automatically installed on said server to handle the Solus 3 environment. On this server it fails with the message that no information could be obtained from the remote machine. It suggests that WMI is not enabled through the firewall but the firewall is not running! So why can't this information be obtained? As I said on all the other installations I have performed this process has gone through without a problem. I think all the servers used have the same configuration but clearly here something is different but I can't find what it is. Of course to find the difference you need to know where to look and this is where I need some help Thanks

The firewall is definitely off. Sophos AV is installed but the firewall in that product is off also. The strange thing is that the set-up seems to be identical to the other 15 servers that I have done and they have all been fine. Clearly there must be something different about this one. I really need a pointer to where I might start to look.

Sorry - Windows Server 2003 R2

I have installed Solus 3 on a number of servers sucessfully. On this particular one (Windows 2003 R2 64bit) the agent that is reposible for the Solus 3 management will not install. The message asks to make sure WMI is enabled through the firewall but the firewall is off. Since this has just worked on several similar servers with identical configurations I am missing a trick here but am at a loss to know what it is What should I be looking for?