Error when deplopying project

[cknott2243]

Hello,

I am new to 3CX so this could be something easy I overlooked.

I installed and configured 3CX last year along with a VAD project to verify callers pin codes and then forward based on the input being valid/invalid. Unfortunately right before putting this in production the whole project was stopped and 3CX was put on hold until recently.

I have installed 3CX v9 on a new server and imported the backup from previously and finished the configuration. Everything is working great except the VAD project. It hangs up instantly with no error that I can see.

I looked through the project again and did not see anything problematic and the same project worked perfectly before. To test I removed the digital receptionist and then tried to build and deploy the project again to see if it was just an issue of it being applied from a backup.

Unfortunately when trying to deploy I receive the error:

"object reference not set to an instance of an object"

I am trying to deploy this as a release build and I see it start uploading one WAV file and then the error is seen.

I cant find any logs that points to anything helpful.

Any ideas out there? I am praying I don't have to build it from scratch because it took me 3 weeks the last time to create this and get it working.

Thanks,

Chris

 

[cknott2243]

Not sure if this is directly related but any error like this would seem to be especially when I am entering the pin/DB validation portion of the app.

btag SBjsiSetVarExpr. entering: 0x0BDB0380, 'project$_CurrentErrorDescription$', ''ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application''

I see this each time I ring into the app and try to enter my pin. The odd thing here is I am using MySQL and ODBC in the project so not sure why Microsoft is throwing an error?

Thanks.

 

[VAD_Support]

It seems that the ODBC connection is not correctly configured. Please take a look at this article for help on how to access a MySQL database from the VAD:
http://www.3cx.com/blog/docs/database-vad-3cx/

This article may also help you configuring your DSN correctly:
http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/702f0d9b-6cb9-49cf-9953-80d059711e60

You mentioned that your server is x64, so depending on your MySQL (x86 or x64) you may need to configure it with the x86 or x64 control panel.

Regards,

 

[cknott2243]

I have done everything I can think of but still get this error. The odd part is nothing is set to use Microsoft, the ODBC is configured to connect to MySQL not MS SQL so not sure why the MS error is even being seen.

I uninstalled MySQL and reinstalled it to ver 5.1 from 5.0.1 and then ODBC 5.1 both 32bit. I use DB's in all other things I do so I know for certain the ODBC is configured properly as other items I create to use it (simple PHP script, etc.) connect without issue.

Is there a specific DB recommended or version? I would rather not use MSSQL for such a small thing. Could try Access maybe.

Let me know what you think. I think it still has to be a bug or something along those lines if it is somehow seeing it as MS instead of MySQL.

Thanks again.

 

[VAD_Support]

Hi Chris,

This is the error message you're getting:
ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

That error mentions Microsoft because ODBC is a Microsoft technology. When you access any database via ODBC, the application talks to a Microsoft layer, then it talks to the database via ODBC. So, the error is there even when you're using MySQL. I know that the article I sent you talks about SQL Server, but the way to fix the problem is the same. Here is another article about this (more generic, not SQL Server):
http://msdn.microsoft.com/en-us/library/ms712362(VS.85).aspx

Pay special attention to this note:
To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, use c:\windows\system32\odbcad32.exe. In Administrative Tools on a 64-bit Windows 8 operating system, there are icons for both the 32-bit and 64-bit ODBC Data Source Administrator dialog box.

You're running 3CX on a 64 bits server. So, the application that queries the database runs in 64 bits mode. That's because it runs under the 3CX web server, into a ASPX page. Your database is 32 bits, so you should configure the ODBC DSN using c:\windows\sysWOW64\odbcad32.exe. Are you using that tool? If you launch it from the control panel you will open c:\windows\system32\odbcad32.exe which is NOT what you need.

Hope you can fix the problem with this information.

Regards,

 

[cknott2243]

Sorry, if I was not clear previously regarding this but I am and have been using the 32bit ODBC manager. I run many DB applications so am well aware of this need.

I have the MySQL ODBC setup in the 32bit manager as it should be which connects without a problem.

Unfortunately I don't see anything else I can do with it already being run from the 32bit manager and being that 3CX is the only thing having an issue with it.

I am not sure if you have your own MySQL server but maybe you could try and see your results.

Please let me know.

Thanks.

 

[cknott2243]

As a last ditch effort I will try to redo MySQL and use only 64bit and see if that changes anything.

 

[VAD_Support]

Why don't trying with MySQL 5.5 - 64 bits? If you're running a 64 bits server, it would be better to use a 64 bits database. That way you avoid this kind of errors.

 

[cknott2243]

It looks like with 64bit SQL it is now accepting it and working properly.

I still don't fully understand why some of the problems were seen but at this point I am happy to just have it working so I can finally deploy 3CX fully.

I really do appreciate the help you have given me, great customer support will be a reason I recommend the product to everyone. I'll let you know if I run into anything else but hopefully not.

Thanks again,

Chris

 

[VAD_Support]

Hi Chris,

Thanks for letting us know that you finally found a way to solve it.

We'll be ready to assist you whenever you need it.

Regards,

 

[cknott2243]

I found one last thing that is strange and different than when it worked before.

Now it works and routes the caller through after putting in a pin code but the problem is it now accepts all input as being valid.

If I use any combination of numbers it allows them through, I have made sure to use a number that does not exist in the DB.

Any ideas?

 

[VAD_Support]

Please, send me the project in its current state again in a PM, so I take a look.
Thanks,

 

[cknott2243]

Ok, thanks. I'll send it shortly.

Thanks again.

 

[cknott2243]

Sent.

 

[VAD_Support]

Hi Chris,

You have a hardcoded PIN value into the SQL query. You're using this query:
SELECT supportpin FROM pin WHERE supportpin='1234'

You should change it with this:
SELECT supportpin FROM pin WHERE supportpin='{0}'

And add a parameter to the database access component:
Name: CustomerPin
Value: callflow$.CustomerPin

Regards,

 

[cknott2243]

Geez, I looked right over that. I added that in there when testing and completely forgot to remove it.

Thanks, I'll add this and should be good to go.

BTW, I have some other issues with 3CX as a whole, is there a support address or just the forum?

Thanks again.

 

[VAD_Support]

You have the forum or you can purchase a support package from 3CX or from any reseller near you.
Remember that the forum is supported mainly by users. For official 3CX support you need to purchase a package. If you're a reseller, then you have the support from 3CX for free using the support portal. More information here:
http://www.3cx.com/blog/support/

 

[cknott2243]

Thanks. Just curious because I havent seen any info on it.

Quick question, I would love to move to v10 before going live, I just purchased the license today to upgrade.

When I am trying to deploy the project (I chose v10 for the project version) I get this error:

Config server not configured

And then fails, any idea?

Thanks as always.

 

[VAD_Support]

Hi Chris,

After changing the PbxType to v10 you need to restart the VAD.

Also, you need to enable remote access to the configuration into 3CX. Have you changed that? You are deploying remotely, right?

Regards,