The error is because the CPOS wasn't able to hit the AX '7' database. The CPOS uses a single AxDB database, in my case in the 'all in one' server, which the CPOS needs to have access to.
The environment was the AX 7 Update 1 using upgraded data from the AX 7 RTW release.
The Update 1 data changed in regards to some setup information. Event Viewer gave me some information into this essentially saying that the axruntimeuser wasn't able to access the DB. This, among other things, led me to believe the channel database setup was wrong.
To reconfigure the channel database 'connection string', you'll need the connection string (duh). I used Visual Studios Server explorer to create a connection to the database with the AxDB database for the CPOS, then clicked 'Properties'. The connection string will be right there. (Figure 1)
Paste this value into the appropriate connection string (Figure 2). Mine was the 'Default' one. Run the 1070 job (I think that's the channel job... if not, run that one).
You'll need to cycle the Retail Server application pool also (Figure 3 below).
There were a few other random settings I had to change from RTW configs to update 1 but the above was the main one. I think there were only 3-4 other places.
Hopefully this helps someone else jump past this issue!
- Getting up to speed on D365/AX
- Dynamics 365 财务和运营 认证考试 / Dynamics 365 for Finance and Operations Certification Exams
- Find product attributes and values for an item in AX 2012 via X++
- MPOS Error: Creating device token failed
- AX POS Permission Groups and Leading Zeros – Solved!
- AX Modern POS (MPOS) Retail Channel Reports missing and setup