Forum

Just figured, that the wrong version of "default.asp" (queue visualization) found it's way into the beta package.

It still contains my test connect string which is definately not valid for you. So just change

    Provider=sqloledb;Data Source=ws-wellige02;Initial Catalog=OpenQueue;User Id=openqueue;Password=openqueue

to

    Provider=sqloledb;Data Source=localhost;Initial Catalog=OpenQueue;Integrated Security=SSPI

Tom Wellige
(Lead Solution Consultant, Swyx)

"It is a capital mistake to theorize before you have all the evidence. It biases the judgment."
Sir Arthur Conan Doyle - Sherlock Holmes - A Study in Scarlet

Hi, the missing vssver.scc is not the cause. The source code control system creates these scc files for book keeping only. That's the reason why Tom hadn't included them in the package.

Concerning the connection: The corrected connection string Tom posted above assumes that you have a SQLServer or MSDE on the same system as SwyxWare and that a database named OpenQueue exists. If that's the case and you still have no access, it's probably related to access permissions to the database. I suggest to check that the SQL logins and database users are correctly configured as described in the manual.

Hi,

I still have this error "Error opening Database! (80004005) [DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied." when I connect to my IIS. I started with a fresh Windows 2003 Server (SP2) with Swyx Server 6.02 installed on it and followed your OpenQueue manual exactly. I'm not a database expert. Can someone help me with the security issue?

Joost

Hello Tom

I have the same problem, the script is installed, but fails, so when i call the user, i get the beep.wav after 5 seconds, and also the web page gives the same error, is there a way to test the connections ?

Best regrds

Tom Larsen

Denmark, M & M Datasystemer

Tom Larsen
(Swyx T.A.G Member )

Competence is Expensive, Incompetence is about double the price.

Joost and Tom,

do you still have problems getting Open Queue up and running ? For the GSE part of Open Queue you can enable tracing on the SwyxServer and have look what happens. You can either enable standard tracing (using the common reg file for server tracing) or just enable script tracing (recommended). To do so use the registry editor (regedt32.exe) and set the following value

HKLM/Software/Swyx/IpPbxSrv/Current Version/Tracing
SrvScript: 6

All other modules should be configured to 2. Of course you can also use the trace flags tool from the SwyxWare CD. In this case set "INFO3" as trace level for the "SrvScript" module and make sure all other modules are configured to "Error".

I also recommend to set a new trace file. Now do just one call into the queue and post the resulting trace here into the forum.

But anyway, I assume you have database security problems which are more easy to fix with the ASP webpage first. So first, you should give the sql authentication of my previous post a try.

Regards, Tom.

Tom Wellige
(Lead Solution Consultant, Swyx)

"It is a capital mistake to theorize before you have all the evidence. It biases the judgment."
Sir Arthur Conan Doyle - Sherlock Holmes - A Study in Scarlet

Tom Wellige wrote    Provider=sqloledb;Data Source=localhost;Initial Catalog=OpenQueue;Integrated Security=SSPI

Tom, I am playing around with the OpenQueue now. It will be no probem using the intended connection-string. But if anyone get the access denied from the MSDE (like I also did) it is because you can not use localhost as data source it must the name of the machine (e.g. swyxserver) the MSDE is installed on. Using the machine name instead of localhost made the webpage run without errors.

But this is not working for the ECR script. Therefor I will suggest to use your alternative connection string 'Provider=sqloledb;Data Source=machinename;Initial Catalog=OpenQueue;User Id=queue;Password=yourpassword' both for IIS and ECR to avoid confusion.

Morten Rokosz
(Swyx T.A.G Member)

Captain of the Golgafrinchan Ark Fleet Ship B

The best way to predict the future is to invent it.

morten.rokosz wrote Therefor I will suggest to use your alternative connection string 'Provider=sqloledb;Data Source=machinename;Initial Catalog=OpenQueue;User Id=queue;Password=yourpassword' both for IIS and ECR to avoid confusion.

That's what I do in my test environment anyway so I wasn't aware of the "localhost" problems in advance. That's the result with configuring and describing something and not having really tested it

Rene is already working on a setup and I will check with him to put in some functionality to create a new database login using sql server integrated security. The setup would need to prompt for a user name and a password and would need to modifiy the used connect strings... I wouldn't like to use some standard login name and password as this would open a security gap on the sql server.

Tom Wellige
(Lead Solution Consultant, Swyx)

"It is a capital mistake to theorize before you have all the evidence. It biases the judgment."
Sir Arthur Conan Doyle - Sherlock Holmes - A Study in Scarlet

ittk wrote The good thing is that the hunting-group "support" needs no user logged in to go into the queue (i couldn't this getting work with the default gse / ecr-scripts and no visual basic code additions).

To be honest I considered this as a bug and have fixed it already for the next beta version. What sense would it make to queue in calls if no one is logged in to take them ?

ittk wrote Another good thing is that there is no need to assign a internal or external number to the group.

This is in fact a standard SwyxWare feature. You don't need to assign any number (internal or external) to a user or group and connect calls to this user or group by simply stating the name. Before SwyxWare v6.0 with the introduction of internal and external numbers (all number were automatically internal and external numbers) this was the only way to configure a user / group that was not reachable from outside.

ittk wrote I can't wait for the next release.

The next release will be another beta release with no new functionality. Is there something special you are waiting for ?

Regards, Tom.

Tom Wellige
(Lead Solution Consultant, Swyx)

"It is a capital mistake to theorize before you have all the evidence. It biases the judgment."
Sir Arthur Conan Doyle - Sherlock Holmes - A Study in Scarlet