Dialogic Download Error

[mediasol]

Hi I have attempted to download the dialogic driver for server 2003 from your web site and when I uncompress the zip I'm getting a error message.

 

Please see attached file.

 

I have downloaded the file 3 times from different computers and different time to ensure it was not file corruption on the download.

 

I'm thinking it maybe a problem when the zip file.

 

Could you check or provide any site for me to download the dialogic driver for server 2003.

[SupportTeam]

How many bytes is the file which you have downloaded?

(the actual file size, not the 'size on disk').

[mediasol]

The size is 329,396,288 bytes

[SupportTeam]

Looks like there was something wrong with the drivers download.

We have now updated the links on the Downloads page. Please go the Downloads page and click on the drivers download link again.

[SupportTeam]

Make sure to refresh the browser's page to make sure the new page with new links is loaded, and not the cached old version of the Downloads page is shown. Just click on the Refresh/Reload button.

[mediasol]

Same issue but different another problem.

 

I have finally got the dialogic software download and working (thank you).

 

However when I download the VG 7.1 and install the program, the VG is not starting.

 

In "screen shot 1" you will see the dialogic cards are working and IVR is not.

In "screen shot 2" you will see I can not start the service.

 

I have checked the server services and voiceguide does not appear.

 

I have upload the install log as well

 

What do I do next?

installLog.txt

[SupportTeam]

Could you please post a copy of VoiceGuide's trace logs which capture the system startup, this will allow us to see what is happening when the service is starting.

 

Debug Trace files are created in VG's \log\ subdirectory.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[mediasol]

There are no trace logs. The Log folder is empty.

[SupportTeam]

Have you tried restarting the machine?

 

If that does not help then can you setup access to this system using www.logmein.com (or similar) and we will quickly log into this system to see what is going on.

Please email login details to support@voiceguide.com and include a link to this support forum thread in your email.

[SupportTeam]

We were able to log into system and fix the issue. Looks like the installer was not correctly registering the VoiceGuide service on this Win2003 machine.

 

Running this command line in the DOS box fixed the issue:

 

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\installutil.exe "C:\Program Files\VoiceGuide\vgIvrService.exe"

 

with the VoiceGuide service now registered and set to start automatically on system restart.

 

Similar problem was affecting vgServices COM registration, so we had to run this from DOS box:

 

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm.exe "C:\Program Files\VoiceGuide\vgServices.dll" /codebase

 

The install log shows that the installer tried to run:

 

Execute: C:\Documents and Settings\Administrator.LEADS\WINDOWS\Microsoft.NET\Framework\v2.0.50727\installutil.exe "C:\Program Files\VoiceGuide\vgIvrService.exe"

Execute: C:\Documents and Settings\Administrator.LEADS\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm.exe "C:\Program Files\VoiceGuide\vgServices.dll" /codebase

 

instead. We had other customers run VG install on Win2003 with no problems, an not sure at this stage why the installer would want to run installutil and regasm from another location. Will look into this and fix installer as required.

[SupportTeam]

Looks like this mixup in Windows directory paths is done by Windows itself if the install is done when using Windows Terminal-Server in application-mode.

 

We'll fix the installer so that installations done over the Windows Terminal-Server login are ok as well. In the meantine to do install while using Windows Terminal-Server, run this first (in DOS window):

 

change user /install

 

and then start installer again. After the installation run:

 

change user /execute

 

or just use logmein or VNC etc to login into the machine instead of using Windows Terminal-Server.

[mediasol]

All working now thanks